You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working in a monorepo, and I have gone to where storybook is housed and ran the npx storybook@latest upgrade or pnpm dlx storybook@latest upgrade or npx [email protected] automigrate @JReinhold
To Reproduce
the directory where storybook is housed and ran the various migrations
this is what happens when i run npx storybook@latest info
System
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN config cache-min This option has been deprecated in favor of `--prefer-offline`.
node:internal/modules/cjs/loader:936
throw err;
^
Error: Cannot find module 'C:\Users\xxxxx\Project\zzzzz\node_modules\@storybook\cli\bin\index.js'
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
at Function.Module._load (node:internal/modules/cjs/loader:778:27)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
at node:internal/main/run_main_module:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi there! Thank you for opening this issue, but it has been marked as stale because we need more information to move forward. Could you please provide us with the requested reproduction or additional information that could help us better understand the problem? We'd love to resolve this issue, but we can't do it without your help!
Describe the bug
I am working in a monorepo, and I have gone to where storybook is housed and ran the
npx storybook@latest upgrade
orpnpm dlx storybook@latest upgrade
ornpx [email protected] automigrate
@JReinhold
To Reproduce
the directory where storybook is housed and ran the various migrations
this is what happens when i run npx storybook@latest info
System
Additional context
No response
The text was updated successfully, but these errors were encountered: