Storybook 5.2 Release 🚀
See original GitHub issueIt’s that time again! Storybook 5.1 is stable and 5.2 is coming down the pipe!
Schedule
- ✅
5.2.0-alpha.0
: 2019-04-29 - ✅
5.2.0-beta.0
: 2019-07-15 - ✅
5.2.0-rc.0
: 2019-08-30 - ✅
5.2.0
: 2019-09-17 (ready on 09-10, delaying to avoid clashing with Apple event)
Contents
- Storybook DocsPage
- React
- Partial support for all frameworks
- Iterate beta feedback
- Documentation
- Component Story Format
- Definition
- Loader
- Codemods
- SB CLI Migration
- Documentation
- Design System
- Component librray
- 3x Apps
- Documentation
- Addon API
- Hooks-based API
- Documentation
- Jest Addon redesign
- Story sorting
- Implementation
- Documentation
- Typescript
- Typings for addons,
@storybook/react
,@storybook/angular
- Typings for addons,
- CLI
--preview-url
for remote preview- Rollup example
- Yarn PnP support?
Full list of changes in CHANGELOG
Help Wanted (Now!)
We need your help stabilizing Storybook 5.2 for the final release. It’s in beta now because we think it’s ready to use in most projects.
The biggest thing is to try upgrading your project to the latest prerelease, see if you run into problems, and file github isues. The sooner we uncover problems with the upgrade, the more time we have to fix and document them.
To upgrade your project:
npx npm-check-updates '/storybook/' -un
npm install # yarn if you prefer
We’ve also started to document migration instructions, and will continue to update the documentation throughout the release.
And of course, if you see any issues that you can help with, PRs are always welcome. Storybook wouldn’t be possible without high-quality contributions from our wonderful community.
Thanks for your help and stay posted for more updates!
Issue Analytics
- State:
- Created 4 years ago
- Reactions:42
- Comments:7 (4 by maintainers)
Top GitHub Comments
Released Sep 13, announcement coming Sep 17
@inlikealion SB Vue support is stable and usable. Vue support SB Docs is also useable but still early. If it’s useful I’d be happy to go through any issues you run into on our Discord and get them sorted out, since the documentation is still sparse. https://docs.google.com/document/d/1un6YX7xDKEKl5-MVb-egnOYN8dynb5Hf7mq0hipk8JE/edit?usp=sharing