[Bug]: Upgrade command results in Cannot find module in C:\....node_modules\@storybook\clib

[AS-EBaiden]

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 or pnpm dlx storybook@latest upgrade or npx storybook@7.6.10 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

[shilman]

Can you provide more information about your setup? Which package manager & version specifically?

[AS-EBaiden]

Can you provide more information about your setup? Which package manager & version specifically?

We built it on a monorepo, our pnpm is our package manager. it is v8.8 which is installed globally

[JReinhold]

This might have been fixed by #25752 released in 7.6.12, could you try running npx storybook@latest upgrade again and see if it works now?

[github-actions]

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!

[AS-EBaiden]

This might have been fixed by #25752 released in 7.6.12, could you try running npx storybook@latest upgrade again and see if it works now?

It is now working as expected, thank you!