-
-
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]: All npx storybook@latest ...
commands fail with Error: Cannot find module './util'
#23220
Comments
I've reported this to the |
Temporary workaround:
|
Thanks for reporting this. I'm unable to reproduce this locally, but I think that's because I'm running MacOS with the default file system which is case-insensitive, so it doesn't get hit by this issue. We're seeing the same errors in our CI right now, eg.: https://app.circleci.com/pipelines/github/storybookjs/storybook/53541/workflows/92543e18-fb1c-4a72-b7bf-9f2431a71b9a/jobs/550427 |
I worked around this in my pnpm monorepo project by having an override defined in the root package.json as:
|
For reproducing linux issues, you can quickly reproduce it by using docker, try: docker run -it --rm node:16 npx -y [email protected] --version It is definitely failing for me |
Hey everyone! We're working on a fix and will be making a release shortly, you can follow the open PR for 7.0.24 or you can currently work around it via overrides in your package.json files, e.g.: pnpm
npm
yarn
And as soon as the new version of Storybook is released, you can remove it and upgrade. |
Hey everyone! We have released Storybook 7.0.24 containing a fix to this issue. Please upgrade and let us know if you have any issues! Thanks for your patience :)) |
Describe the bug
After getting this error when trying the
npx storybook@latest init
command on my NextJS project, I cleared NPM/NPX caches, and also tried on a brand new blank project, and it failed with the same message each time.To Reproduce
npx storybook@latest init
System
> Please paste the results of npx storybook@latest info here. I get the same error when running that. - Linux (Ubuntu 22.04.2) - Node v18.16.1 - NPM v9.5.1
Additional context
No response
The text was updated successfully, but these errors were encountered: