chore(storybook): upgrade to storybook 7 #978
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #955
Proposed Changes
upgrade storybook to latest (7.0.21) to fix the docPage copy bug (see here: storybookjs/storybook#18611 (comment))
Breaking Changes/ToDos:
Migrate .stories.mdx files to MDX2:
Completed the automated upgrade of the 64 .stories.mdx files from MDX1 to MDX2 format as prompted by Storybook. Please refer to the MDX2 section of the 7.0 migration guide for details.
Upgrade to Storybook's 7 New Framework Format:
Migrated the project to use Storybook's new framework: @storybook/web-components-webpack5. This involved:
Removing the dependencies: @storybook/builder-webpack5 and @storybook/manager-webpack5.
Adding the dependency: @storybook/web-components-webpack5.
Updating the framework field in main.js to use @storybook/web-components-webpack5.
Removing the core.builder field in main.js.
More about this new framework format can be found here.
Eslint Recommendations:
In case we face any issues, we can always run the npx storybook@latest automigrate script to get the recommended ESLint configurations provided by Storybook.