CLI: Add Next.js framework automigration #19574
Conversation
| return null; | ||
| } | ||
|
|
||
| // we only migrate from react-webpack5 projects |
There was a problem hiding this comment.
Given that @storybook/react-webpack5 is only available in 7.0+, It seems far more likely that someone would be upgrading from a project with @storybook/react & @storybook/builder-webpack5. Perhaps, for this scenario, we could leverage the fix tested here, and then re-run this fix?
There was a problem hiding this comment.
This would happen after another migration that would have migrated users to react-webpack5
| This package provides a better experience for Next.js users, however it is only compatible with the webpack 5 builder, so we can't automigrate for you, as you are using the Vite builder. | ||
|
|
||
| If you are interested in using this package, see: ${chalk.yellow( | ||
| 'https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#nextjs-framework' |
There was a problem hiding this comment.
Let's just point them to the framework README. I don't think that info belongs in the migration guide.
shilman
changed the title
|
Decided to leave this until after the post has gone out & somebody has time to properly test it |
|
I based the SvelteKit automigration on this work, with some modifications. Feel free to be inspired or ignore it. |
yannbf
force-pushed
the
nextjs-automigration
branch
from
c131e01
to
ec2ab18
Compare
Issue: N/A
What I did
This adds an automigration for projects using
@storybook/react-webpack5and Next.js, so they can use the new@storybook/nextjspackage instead.For
@storybook/react-viteand Next.js users, it will warn them, but not migrate anything:TODO:
How to test
sb automigratein a React Webpack5 + Next.js projectIf your answer is yes to any of these, please make sure to include it in your PR.