Skip to content
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 6.0 Release πŸ† #9311

Closed
shilman opened this issue Jan 3, 2020 · 29 comments
Closed

Storybook 6.0 Release πŸ† #9311

shilman opened this issue Jan 3, 2020 · 29 comments
Assignees
Milestone

Comments

@shilman
Copy link
Member

shilman commented Jan 3, 2020

Storybook 6 is now in RC! That means all of the breaking changes are in, and we don't expect any destabilizing changes between now and the final release, just lots of cleanup and bug fixing (famous last words...)

Schedule

  • βœ… 6.0.0-alpha.0 2020-01-21
  • βœ… 6.0.0-beta.0 2020-04-29
  • βœ… 6.0.0-rc.0 2020-07-08
  • 🏁 6.0.0 2020-08-10

Contents

6.0 RELEASE POST

6.0 contains hundreds more fixes, features, and tweaks. Browse the changelogs matching 6.0.0-alpha.*, 6.0.0-beta.*, and 6.0.0-rc.* for the full list of changes. See MIGRATION.md to upgrade from 5.3 or earlier.

PRs and other docs of interest:

Help wanted

We'd love your help testing out the new features, and will be documenting them here.

Migration guide

To upgrade all your @storybook/* packages to the latest pre-release, run:

npx sb@next upgrade --prerelease

We'll provide a user-friendly migration guide for 6.0. In the meantime, there's an exhaustive list of potentially breaking changes in MIGRATION.md. Most of the breaking changes have been deprecated for months, and most of the future breaking changes are implemented as backwards-compatible deprecations for now. So, while the list of breaking changes is long and scary-looking, in practice we expect most upgrades to succeed without much extra fiddling.

Storybook Args

Args are a new concept in Storybook's Component Story Format. We've prepared an RFC to explain the idea, the feature links above and updated CSF documentation.

On the more practical side, we have a a walkthrough to get you going with the initial implementation], and an open PR to add args to Storybook's Design System.

MORE HERE SOON

Thanks for your help and stay posted for more updates!

@shilman shilman added this to the 6.0.0 milestone Jan 3, 2020
@chrisabrams
Copy link

5.3 introduced major changes even though it was a minor version release so not really sure what y'alls definition of major is.

@shilman
Copy link
Member Author

shilman commented Jan 16, 2020

@chrisabrams which major changes?

@chrisabrams
Copy link

We used to be able to provide addons as a function that returns an array; starting in 5.3 addons only supports an array it does not check to see if there is a function anymore. This broke all of our storybook setups (we have 100s setup this way).

@shilman
Copy link
Member Author

shilman commented Jan 16, 2020

@chrisabrams I see. Try renaming addons to managerEntries in your presets. We'll document this unintended breaking change in the migration guide. cc @ndelangen

@eroane-rms
Copy link

Hi @shilman! I'm very excited about 6.0 beta! During the alpha phase I have been following the Composition feature closely and almost managed to patch a bug in it along the way 😁

Can you share documentation about how you expect composition to work so I can report my findings on it better? My interest in it comes from my my use case. I want to compose multiple storybooks in a monorepo together and test the composed storybook in Chromatic as a single project.

To do this do I need to host each statically built storybook before composing? That is how it seems to work in the dev-kits example. Or will the cli bundle them together? How will the storybooks that are being composed generate their metadata.json and stories.json files?

Please let me know how I can help, I'd love to!

@adeelibr
Copy link

Thank you for all the amazing work you are doing. πŸ‘ πŸ’―

@ndelangen
Copy link
Member

@eroane-rms writing documentation about composition is on my task-list.

I expect to finish it next week.

@eybbus
Copy link

eybbus commented May 20, 2020

Hi, what is the current estimate on release of 6.0.0? My team were planning on moving from 5.2 to 5.3 but saw that 6.0 was scheduled to release yesterday.

@ndelangen
Copy link
Member

We' working on some more docs, there's been talks of overhauling the docs-site even.

I'm working on fixing a list of bugs on the composition feature relating to CORS & auth.

There's also work being done to make storybook 6 auto-compatible with typescript (0-config)

And there's more delaying the release.. @shilman has some more info on this.

I'd say migrating to 5.3 is a good idea: you added deprecation warnings to certain things in 5.3.x on things we removed in 6.0. So you can be prepared for when those api's do drop.

See the CHANGELOG & MIGRATION guides

https://github.com/storybookjs/storybook/blob/next/MIGRATION.md
https://github.com/storybookjs/storybook/blob/next/CHANGELOG.md

@shilman
Copy link
Member Author

shilman commented May 20, 2020

Thanks @ndelangen. Yeah, working on an updated estimate now.

The big remaining items are:

  • Stabilization of newly-added features
  • Typescript support improvements (more on this soon)
  • Documentation site updates
  • Release packaging

@hipstersmoothie
Copy link
Contributor

I love the addition of being able to choose the docgen! Is there any way currently to edit the options without a main.js?

@shilman
Copy link
Member Author

shilman commented Jun 6, 2020

@hipstersmoothie Nope. We're all in on main.js, so upgrade today (I'll write up a friendly upgrade guide as part of the 6.0 release). I think we're deprecating config.js in 6.0 and might remove it in 7.0.

@nnennajohn
Copy link

Hi @shilman, I got here from this thread: #7066 (comment)

Is there now a way to make the Docs tab default? Thank you.

@ghengeveld
Copy link
Member

@nnennajohn See #7066 (comment)

@openscript
Copy link

@nnennajohn See #7066 (comment)

That removes the Canvas tab and doesn't make Docs the default tab.

@ghengeveld
Copy link
Member

@nnennajohn See #7066 (comment)

That removes the Canvas tab and doesn't make Docs the default tab.

It will basically hide the UI tabs and panels and show the docs view by default. You can still toggle the UI tabs' and panels' visibility using keyboard shortcuts though.

It's the only option you have right now. We want to improve this but there's a lot of higher priority things. A pull request is welcome though πŸ‘

@nnennajohn
Copy link

@ghengeveld ok. Thanks for pointing me to a solution.

@saravvij
Copy link

npx sb@next upgrade --prerelease - Upgrades storybook to alpha. How to upgrade storybook 5.x to rc release?

@shilman
Copy link
Member Author

shilman commented Jul 21, 2020

@saravvij npx sb@next upgrade --prerelease upgrades any version of storybook to the RC release. We'll publish a migration guide soon, but in the meantime the best resource for breaking changes etc. is https://github.com/storybookjs/storybook/blob/next/MIGRATION.md

@cescoferraro
Copy link

cescoferraro commented Jul 21, 2020

@shilman any tips on how to run it with typescript?
I thought i was having issues with the wrong library.
I am getting some errors like described on the link below
ccontrols/component-controls#6
i am running this on a pretty young next.js codebase

@shilman
Copy link
Member Author

shilman commented Jul 22, 2020

@cescoferraro this is an umbrella issue for the 6.0 release. Please open a separate issue describing your specific problem and we'll do our best to help there!

@tknickman
Copy link
Contributor

Just chiming in to say we recently upgraded our storybook covering a big monorepo with custom webpack configs from 5.3.x to the latest 6.0 RC's (npx npm-check-updates '/storybook/' -n -u && npm install) and after the minimal changes following the migration docs everything is running great AND it fixed all the issues we were having with addon-docs (missing story source and missing prop-types).

kudos and can't wait for the full release πŸ‘

@jimmyandrade
Copy link
Member

jimmyandrade commented Aug 4, 2020

Wow, looking forward for this ❀️

@jlawanson
Copy link

We' working on some more docs, there's been talks of overhauling the docs-site even.

I'm working on fixing a list of bugs on the composition feature relating to CORS & auth.

There's also work being done to make storybook 6 auto-compatible with typescript (0-config)

And there's more delaying the release.. @shilman has some more info on this.

I'd say migrating to 5.3 is a good idea: you added deprecation warnings to certain things in 5.3.x on things we removed in 6.0. So you can be prepared for when those api's do drop.

See the CHANGELOG & MIGRATION guides

https://github.com/storybookjs/storybook/blob/next/MIGRATION.md
https://github.com/storybookjs/storybook/blob/next/CHANGELOG.md

Hello @ndelangen Thank you for all your work! I wanted to check in and see how you're coming along with the CORS bugs on the composition feature because I am still getting errors.

@shilman shilman mentioned this issue Aug 10, 2020
2 tasks
@rannyeli
Copy link

Experiencing some CORS issue in 6.0.0-rc while using storybook composition feature.
I'm adding a ref for a local storybook:

refs: {
    react_components: { 
      title: "React Components", 
      url: "http://localhost:9010"
    },

The local storybook works well on port 9010, but not loaded from the combined storybook
image

dev-tools output:
image

@PazDak
Copy link

PazDak commented Aug 10, 2020

Is 6.0.0 still planning on general release today?

@ghengeveld
Copy link
Member

ghengeveld commented Aug 10, 2020

Expected Monday afternoon/evening US time. Basically when @shilman wakes up in Taiwan.

@ghengeveld
Copy link
Member

ghengeveld commented Aug 11, 2020

It's published πŸš€

@shilman
Copy link
Member Author

shilman commented Aug 11, 2020

πŸ’₯ release post coming πŸ”œ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests