2acb53bd30
**What's the problem this PR addresses?** A decent amount of the examples don't have a `name` field in `package.json` that matches their folder name, meaning they either lack a name or the names are duplicated. I was testing Yarn 2 workspaces using the entire examples directory and needed to get rid of the duplicates. **How did you fix it?** Updated the names to match the names of their folders |
||
|---|---|---|
| .. | ||
| pages | ||
| .babelrc | ||
| .gitignore | ||
| package.json | ||
| README.md | ||
With styled-jsx SASS / SCSS
Next.js ships with styled-jsx allowing you to write scope styled components with full css support. This is important for the modularity and code size of your bundles and also for the learning curve of the framework. If you know css you can write styled-jsx right away.
This example shows how to configure styled-jsx to use external plugins to modify the output. Using this you can use PostCSS, SASS (SCSS), LESS, or any other pre-processor with styled-jsx. You can define plugins in .babelrc. This example shows how to implement the SASS plugin.
More details about how plugins work can be found in the styled-jsx readme
Deploy your own
Deploy the example using Vercel:
How to use
Execute create-next-app with npm or Yarn to bootstrap the example:
npx create-next-app --example with-styled-jsx-scss with-styled-jsx-scss-app
# or
yarn create next-app --example with-styled-jsx-scss with-styled-jsx-scss-app
Deploy it to the cloud with Vercel (Documentation).