-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Storybook 7.0 #13491
Comments
Due to compatibility reason, we should currently work with PostCSSv7, because Storybook is not up-to-date and use this version. Using v8 causes some instabilities in the stack. Cf: storybookjs/storybook#13491
Due to compatibility reason, we should currently work with PostCSSv7, because Storybook is not up-to-date and use this version. Using v8 causes some instabilities in the stack. Cf: storybookjs/storybook#13491
Due to compatibility reason, we should currently work with PostCSSv7, because Storybook is not up-to-date and use this version. Using v8 causes some instabilities in the stack. Cf: storybookjs/storybook#13491
Due to compatibility reason, we should currently work with PostCSSv7, because Storybook is not up-to-date and use this version. Using v8 causes some instabilities in the stack. Cf: storybookjs/storybook#13491
Due to compatibility reason, we should currently work with PostCSSv7, because Storybook is not up-to-date and use this version. Using v8 causes some instabilities in the stack. Cf: storybookjs/storybook#13491
Due to compatibility reason, we should currently work with PostCSSv7, because Storybook is not up-to-date and use this version. Using v8 causes some instabilities in the stack. Cf: storybookjs/storybook#13491
Guys, why these are dependencies, not peer dependencies? At least, consider to ship another package for full-control-mode only – we dont need any defaults for webpack or postcss in our projects. |
Actually, same problem was for React17, and we waited for weeks for 6.1 version of storybook. Consider to use |
Hey! I could not find information: will the As far as I can tell packages |
@dartess yes, SB7 will probably ship with no builder by default and you'll need to choose between webpack4, webpack5, vite, or something else. |
Will storybook@7 support pnpm package manager? |
Is there any ETA for Storybook v7? We would really like to get rid of all the deprecated dependencies that get pulled in due to webpack4. |
Is there a list of browsers that are supported in version 7? I heard you are planning to drop IE11 (what about Legacy Edge?). Do you have a target list of browsers and their versions that will be supported? |
@dartess here's a recent slide from a monthly roadmap meeting that discusses the breaking changes in 7.0 to browser and node support: https://docs.google.com/presentation/d/187z_4QySXzrPReEpIYhdKWgwQDWMpxSNI0ZXb1NVXUo/edit#slide=id.g14ffbccc1fa_0_33 TL;DR: Storybook will support "modern browsers" (Chrome 100+, not sure about the details on Safari, Firefox, etc.), and Node 14+. |
Closing this for now, as the changes mentioned are already a part of the recent Storybook 7.0 release. @shilman let me know if I'm missing something and I'll gladly re-open it |
We're accumulating a number of breaking or highly disruptive changes in the package ecosystem that might require a major release. Collecting them here to explore a 7.0 release or possibly a long-running prerelease that allows us to unblock users.
The text was updated successfully, but these errors were encountered: