fix: try to prevent npm update issue #2894
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.
What I did
I'm entering a dangerous zone here, but some fix is needed and testing it with local
npm link
or prereleases I think is not a good idea, so gonna test with a proper release.Supporting both Storybook 7 and 8 within the same package with
peerDependencies
is not working.npm update
gives an error currently in a project where Storybook 7 is used with@web/mocks
and@web/storybook-builder
So now trying with normal dependencies, which is actually even logical, because storybook doesn't really have to install the packages in question itself, it's more for the addons to do since they use them, so using peer deps was not a good idea to begin with.