-
Notifications
You must be signed in to change notification settings - Fork 686
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
Upgrades Storybook to major version 4 #508
Conversation
This pull request is automatically deployed with Now. |
Thanks for your contribution! It would appear that @zetlen Any idea why it wouldn't pick up the module from the main repo's |
1883568
to
ced46cb
Compare
Super weird. It may be that the versions are incompatible--can you try upgrading |
That was it! I upgraded I also bumped |
I updated the PR description with the new solution and outlined a potential risk. |
3e63d9b
to
aadd90c
Compare
For completeness
I did try this and it did not work without also bumping |
This PR is a:
[ ] New feature
[ ] Enhancement/Optimization
[ ] Refactor
[x] Bugfix
[ ] Test for existing code
[ ] Documentation
Summary
When this pull request is merged, it will fix the current error that is causing Storybook to be unable to load any component stories:
Additional information
The reason Storybook errors out like this is that the
storybook-readme
addon that we are attempting to usewasn't listed as a dependency incouldn't be found.package.json
and therefore was not installed.I bumped Storybook (
@storybook/react
) andstorybook-readme
to major version4
inpwa-studio
and updated Storybook inpackages/peregrine
andpackages/venia-concept
to match.Storybook now finds the
storybook-readme
addon at the higher level and therefore it does not need to be listed as a dev dependency inperegrine
.After this change, Storybook works as intended:
Potential Risk
Upgrading Storybook outside of the
peregrine
project may introduce some breakages.I couldn't find anywhere else in
pwa-studio
orpackages/venia-concept
where Storybook was actually being used though, so I think the risk is none.But with that being the case, should we remove the Storybook dependency from
packages/venia-conept
?Note!
This PR is opened against the
release/2.0
branch. If this is incorrect, kindly let me know and I'll point it to a different branch 🥂 .