-
-
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]: storybook@next init
fails on svelte(-kit) project
#28475
Comments
The error References/code/lib/cli/src/initiate.ts
|
This should be fixed in 8.2.0. Can you please try it out? |
This is resolved! |
I had the same problem with storybook if using react 17 version. Just update to the latest one. |
Same problem today in my React 18 + SB 8.2 codebase.
|
Also getting the same exact output/problem in my Angular CLI 17.2.3 + Node: 18.15.0 codebase |
getting this in Vue3+Vite project as well |
Describe the bug
Looks like this is only happening on the beta build @8.2.0-beta.0.
The cli fails with an unexpected error:
Relates #27096
Relates #28474
Relates svelte-add/svelte-add#475
Reproduction link
https://github.com/manuel3108/storybook-missing-packages-repro (Reused from related issue)
Reproduction steps
test-2
npx storybook@next init
Exception details:
An error occurred while installing dependencies:
wnt.default is not a function
⠏ Installing Storybook dependencies
attention => Storybook now collects completely anonymous telemetry regarding usage.
This information is used to shape Storybook's roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://storybook.js.org/telemetry
Even easier is to have a look at this CI output: https://github.com/manuel3108/storybook-missing-packages-repro/actions/runs/9825360106/job/27125418556
System
(from CI) Storybook Environment Info: System: OS: Linux 6.5 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish) CPU: (4) x64 AMD EPYC 7763 64-Core Processor Shell: 5.1.16 - /bin/bash Binaries: Node: 20.15.0 - /opt/hostedtoolcache/node/20.15.0/x64/bin/node Yarn: 1.22.22 - /usr/local/bin/yarn npm: 10.7.0 - /opt/hostedtoolcache/node/20.15.0/x64/bin/npm <----- active pnpm: 9.4.0 - /opt/hostedtoolcache/node/20.15.0/x64/bin/pnpm Browsers: Chrome: 126.0.6478.126
Additional context
Very similar issue to #28474. The difference is that this issue even happens without adding any additional commands, and the generated exception is a totally different one from the related issue.
The text was updated successfully, but these errors were encountered: