I see lots of support issues where users are using a variety of different @storybook/* package versions, e.g. 5.0.x, 4.0.x, 5.2.0-alpha.x all mixed together.
We should check for this on load and warn them to upgrade to the same version.
Automention: Hey @Keraito, you've been tagged! Can you give a hand here?
@jamesgeorge007 Any interest in taking a crack at this?
@shilman sure would be great if you could elaborate it further :clap:
@jamesgeorge007 For example, a user might have the following packages installed in their project:
@storybook/[email protected],
@storybook/[email protected],
@storybook/[email protected],
While this is OK from a semver standpoint (theoretically these packages might work together since they are all the same major version), we want users to be using the same versions of @storybook/*. So in this case we'd prefer them to upgrade all their packages to match. This will minimize the chances of bugs due to weird version differences:
@storybook/[email protected],
@storybook/[email protected],
@storybook/[email protected],
I think a warning on the CLI when they start-storybook or build-storybook.
I filed the issue because I see this all the time when I'm trying to support storybook users. If everybody's using consistent versions, it will result in fewer support issues and fewer steps in the support process.
One tricky thing is that we have other packages, like @storybook/design-system that are not part of the monorepo and are on a different versionings schedule.
Related to #4617?