Move storybook packages to peer deps #101
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had a test failure begin in storybookjs/builder-vite#357 when updating the test-runner to anything higher than 0.0.5-next.0. I traced it down to the test-runner installing and using a 6.4 version of @storybook/store, while my storybook project is on 6.5.0-beta.0.
I think this change is the correct way to handle this, by moving the storybook projects to peerDependencies, with a range that includes 6.5.0 pre-releases. Any other approach risks installing a different version for the test runner than what is installed in the main project.
📦 Published PR as canary version:
0.0.8-canary.101.df0a2dc.0
✨ Test out this PR locally via:
Version
Published prerelease version:
v0.0.8-next.1
Changelog
🐛 Bug Fix
📝 Documentation
Authors: 3