Open valentinpalkovic opened 7 months ago
Latest commit: 42246423a5262d372357625daf7fff66014a26d3
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Name | Link |
---|---|
Latest commit | 42246423a5262d372357625daf7fff66014a26d3 |
Latest deploy log | https://app.netlify.com/sites/astro-preview/deploys/65d85af8fd15740008e24e29 |
Name | Link |
---|---|
Latest commit | 42246423a5262d372357625daf7fff66014a26d3 |
Latest deploy log | https://app.netlify.com/sites/astro-stencil/deploys/65d85af83ab3b4000897702d |
Brief Description
As one of the core maintainers of Storybook, I have randomly picked your Storybook to upgrade from Storybook 6 to 8 (prerelease). We do this regularly to test different projects and ensure the upgrade and migration experience is smooth and painless. Your project has a lot of
stories.mdx
files; therefore, I have mainly concentrated on migrating them to the new CSF + MDX approach and adjusting ourmdx-to-csf
codemod to accommodate more cases.You can adjust this PR, merge, or close it.
Storybook starts, and the stories and MDX pages are accessible. I don't guarantee that every Story is working as expected, though. Further QA may be necessary. Please reach out if you have any questions!
The whole 8.0 migration notes can be found here. The official 8.0 migration guide is here.
Upgrade steps
npx storybook@next upgrade
(modified - some of the upgrade adjustments are not available on the latest prerelease yet)npx storybook@next migrate mdx-to-csf --glob "**/*.stories.mdx"
.stories.mdx
files to mdx + csf. For more information please visit the migration guide here and here. The codemod was run in a modified form, because during the migrations bugs popped up which were fixed along the waymdx-to-csf
codemod hasn't accounted for.Just to let you know, MDX was upgraded from v1 to v3. The major version bump from v1 to v2 was pretty significant and therefore some MDX pages might look misaligned. Please take a look at the MDX 1 to 2 migration guide here (Storybook 6 to 7 migration guide) and here for more information. The migration from MDX v2 to v3 was smooth in comparison.
JIRA Link
Related Issue
General Notes
Motivation and Context
Issues and Limitations
Types of changes
Checklist