[QA] CLI improvement

[vanessayuenn]

CLI improvement

Feature owner: @JReinhold

Please comment in this discussion thread for any bug report and feedback for this feature as you test out Storybook 8. Kindly adhere to the following format:

Project: Name of your project as entered in Notion
Version: The version of storybook you tested with
Bug/feedback: Details of the bugs/feedback you have

Feature owner should triage the comments here frequently and open issues as needed.

[JReinhold]

Project: SvelteUI
Version: 8.0.0-alpha.13
Bug/feedback:

The upgrade command changed the format in package.json, going from tab indentation to 2-spaced indentation throughout the file.

[vanessayuenn]

#25812

[yannbf]

Project: MealDrop
Version: 8.0.0-alpha.14
Bug/feedback:

storybook@next upgrade does not upgrade satellite packages, leading to duplicated dependencies (with possibly different major versions) after upgrading.

Details and repro are discussed in the issue:
#25731

[valentinpalkovic]

Project: React Vite sandbox with yarn pnp
Version: 8.0.0-alpha.14
Bug/feedback: Upgrading Storybook from version 0.0.0 to version 8.0.0-alpha.14

It seems that the initial Storybook version cannot be detected. I guess it has something to do with yarn pnp mode.

[JReinhold]

This should be fixed now, could you try again?

[vanessayuenn]

tracked here: #25811

[valentinpalkovic]

Related issue: #25770

[jonniebigodes]

Project: Any (it affects core frameworks)
Version: 8.0.0-alpha.14
Bug/feedback: Adding satellite addons via the add command fails to install

If a user runs the add command to enable the Webpack-based packages mentioned in the following documentation (i.e., @storybook/addon-webpack5-compiler-babel and @storybook/addon-webpack5-compiler-swc) leads to the CLI failing to install them with the following errors:

Based on my understanding of Storybook's CLI, it will try and match the version specified and tie it to the addon's version. Since there's no latest or next versions (e.g., 7.6, 8.0 ), it will error out.

One caveat that I checked was that suffixing the package with the latest version (i.e., npx storybook@latest add @storybook/[email protected]) it works

However, replacing latest with next and suffixing the package version, it errors out.

This will probably have compound effects on other packages, such as the coverage addon.

If we're committed to introducing the add command as the method a user should install addons, we'll need to get a better understanding of what's behind this and how best to address it.

In the interim, I would appreciate some feedback on this so that the documentation can be adjusted accordingly, as I worked on them alongside with @valentinpalkovic. Thanks in advance

cc @shilman , @yannbf

[valentinpalkovic]

Filed here #25790