This is leading to duplicate dependencies due to dependencies upon incompatible package version ranges. Specifically, I found that I'm stuck on @storybook/types@7.6.10, @storybook/channels@7.6.10 and @storybook/core-events@7.6.10 because the latest release of @storybook/addon-designs, v7.0.9, references them.
Affected design types
Describe the bug
The latest version of @storybook/addon-designs published to npm is 7.0.9. More precisely, the available releases are:
This is leading to duplicate dependencies due to dependencies upon incompatible package version ranges. Specifically, I found that I'm stuck on
@storybook/types@7.6.10
,@storybook/channels@7.6.10
and@storybook/core-events@7.6.10
because the latest release of@storybook/addon-designs
, v7.0.9, references them.How to reproduce the bug?
Create any app with Storybook, depending on both
@storybook/addon-designs@7.0.9
and@storybook/react@latest
, e.g.:Now run
npm install && npm run storybook:doctor
and you should get a message along these lines, showing duplicated dependencies:Expected behaviour
I should be able to run
npx storybook@latest upgrade
without finding individual packages to be causing duplicated dependencies.Environment
Affected versions
7.0.9, 7.0.10--canary.cae3482.0
Storybook versions
7.6.14