db214214d6
### What? Update Babel packages across the board ### Why? Since you ship vendored presets and plugins it's impossible for people to update this stuff at their own pace - independently from Next. So users of `next/babel` are currently stuck with old versions and, for example, they might not be able to use the TS `satisfies` operator. ### How? I just updated ranges (to pinned ones) where I could find them, run `corepack pnpm i` and re-run build scripts in the `packages/next`. Fixes #43799 |
||
|---|---|---|
| .. | ||
| .storybook | ||
| components | ||
| pages | ||
| public | ||
| stories | ||
| styles | ||
| .babelrc | ||
| .gitignore | ||
| next-env.d.ts | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
Example app with Storybook setup for SCSS in Styled-jsx
This example shows Styled-jsx (with SCSS) working for components written in TypeScript rendered both inside and outside of Storybook.
Deploy your own
Deploy the example using Vercel or preview live with StackBlitz
How to use
Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:
npx create-next-app --example with-storybook-styled-jsx-scss with-storybook-styled-jsx-scss-app
yarn create next-app --example with-storybook-styled-jsx-scss with-storybook-styled-jsx-scss-app
pnpm create next-app --example with-storybook-styled-jsx-scss with-storybook-styled-jsx-scss-app
Run Storybook
npm run storybook
# or
yarn storybook
Build Static Storybook
npm run build-storybook
# or
yarn build-storybook
You can use Vercel to deploy Storybook. Specify storybook-static as the output directory.
Notes
This example combines the following examples, with some required extra config added: