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

[Feature]: migrate to Storybook 7 #30858

Closed
11 of 12 tasks
Hotell opened this issue Mar 22, 2024 · 3 comments · Fixed by #32018
Closed
11 of 12 tasks

[Feature]: migrate to Storybook 7 #30858

Hotell opened this issue Mar 22, 2024 · 3 comments · Fixed by #32018

Comments

@Hotell
Copy link
Contributor

Hotell commented Mar 22, 2024

Library

all

Describe the feature that you would like added

our repo is long overdue for latest SB migrations

Tasks

Things to revert as part of migration:

Closes

Have you discussed this feature with our team

v-build

Additional context

No response

Validations

  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Priority

None

@Hotell Hotell changed the title [Feature]: migrate to Storybook 7/8 [Feature]: migrate to Storybook 7 Mar 22, 2024
@radium-v
Copy link
Contributor

Storybook 7 should be skipped in favor of Storybook 8, which has a more stable plugin API (including better support for web components).

@levithomason
Copy link
Member

Agree, any reason not to go as green as possible here @Hotell?

@Hotell
Copy link
Contributor Author

Hotell commented Jun 25, 2024

  • our vr-testing solution doesn't support storybook 8 so that's a showstopper for now
  • as a general scalable migration practice we migrate 1 major at a time - v8 is planned ofc once we will be unblocked

Storybook 7 should be skipped in favor of Storybook 8, which has a more stable plugin API (including better support for web components).

can you provide more details on "more stable plugin API" ?

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

Successfully merging a pull request may close this issue.

4 participants