-
Notifications
You must be signed in to change notification settings - Fork 1
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] CLI error #6
Comments
same error in macOS with pnpm (in a next.js app): throw error;
^
Error: spawn pnpm dlx ENOENT
at __node_internal_captureLargerStackTrace (node:internal/errors:496:5)
at __node_internal_errnoException (node:internal/errors:623:12)
at ChildProcess._handle.onexit (node:internal/child_process:284:19)
at onErrorNT (node:internal/child_process:477:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess._handle.onexit (node:internal/child_process:290:12)
at onErrorNT (node:internal/child_process:477:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn pnpm dlx',
path: 'pnpm dlx',
spawnargs: [ '@storybook/auto-config', 'styling' ]
}
Node.js v18.18.0 |
Same here MacOS. Fresh installation of storybook
|
Hey everyone! Sorry about the wait. I've been away for a few weeks and trying to get back on top of my notifications. I'll dive into this over the next few days to see what's happening. |
My case is solved. I used Tailwind and seems this package is not supporting it. Moving to: @storybook/addon-themes solved it. Mistake comes from deprecated package description: Error message could be more intuitive |
Hey @CilooW I just published a fix that should solve your problem on Windows. Can you give |
@integrayshaun unfortunately, I installed manually the addon by copying the line in my package.json, because the install with cli didn't work (npm, says no target found, as if the package didn't exist). |
Hey @CilooW I'm sorry that this is still a problem for you :( despite the error being the same, can you share the output with me? I just want to confirm that your machine isn't using an old cache from the previous npx attempts. |
@CilooW that's odd. it shouldn't be trying to install v7.1.1 of the styling-webpack addon because we're only on version 0.0.5 This tells me that your npx command is using version 7.1.1 of storybook instead of the latest which was 7.4.6 when you sent this 🤔 |
@jacob-granular Can you give me more information about your storybook? Copy and paste the result of |
Hey guys! I got the same issue reported by @jacob-granular .. here's the output of
cc: @integrayshaun |
@integrayshaun I've updated my comment above with the output. The only way i've managed to get storybook working with post-css is to include custom webpack config in
|
I got the same issue, I wanted to configure it for styled-components
I also tried commiting the uncommitted changes but then it ends without doing anything:
|
Describe the bug
I want to change preset/scss in my projet , with this addon. I installed the storybook CLI. Then, I get an error when installing addon with the Storybook CLI
Steps to reproduce the behavior
npx storybook@latest add @storybook/addon-styling-webpack
Expected behavior
I should have the new addon installed
Screenshots and/or logs
Environment
Additional context
I look for a simple solution to uninstall preset/scss and have something else in my package to handle scss preprocessing, as I run into scss duplicating, especially for the global part... and I was hoping maybe this addon could help me resolve my problems :) .
The text was updated successfully, but these errors were encountered: