-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: "No package matched your request" from storybook upgrade
in monorepo
#26421
Comments
Hey @joshkel would you mind explaining a bit better on how to set up a reproduction for your issue? That would be highly valuable for us. If you have or can set up a repro you can share, that would be even more appreciated! |
I have the same issue. My audit failed with the following:
So I have tried to perform the upgrade and I get this:
|
@robinelvin thanks for reporting! Would you mind giving a minimal reproduction? Are you maybe in a monorepo and have Storybook set up in a specific directory, but ran the upgrade command in the root? Can you give as much detail as possible into how this happened? |
@yannbf Thanks for the quick response. I do indeed have a monorepo and I did run the command in the root. I have since run the command in the relevant package directory and have successfully performed the upgrade. So this was my mistake but there are no instructions that I can see at Storybook - Automatic Upgrade that mention monorepo steps. Also, the error that is thrown isn't informative. If it were possible to detect a monorepo setup by perhaps finding the I think my confusion came from the fact I always use Thanks |
I'm getting the same error :( Is there anyone who can help me?
|
Describe the bug
I tried upgrading Storybook to version 8, following the migration guide, and got errors similar to the following:
The problem appears to be caused by our monorepo setup: only one of the projects in our monorepo has a React UI, so the various Storybook packages are only listed as dependencies of one of the monorepo components, not of the top-level
package.json
.I believe that changing
yarn info --name-only --recursive
toyarn info --name-only --recursive --all
should address this; see docs.To Reproduce
No response
System
Additional context
No response
The text was updated successfully, but these errors were encountered: