Compatibility with npm 7
See original GitHub issueI am currently trying to publish storybook but the process keeps hanging on step 6: Building your Storybook.
I tried running the build-storybook command alone and then it works.
build-storybook -- --output-dir /var/folders/b6/g83mw8h9531btnbcmd3s7dh80000gn/T/chromatic--84494-mYwHeFxGFSLu
I checked the build-storybook.log generated and it gives me this message.
Starting: --silent build-storybook -- --output-dir /var/folders/b6/g83mw8h9531btnbcmd3s7dh80000gn/T/chromatic--84494-mYwHeFxGFSLu
node: bad option: --silent
Thanks in advance for the help!
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
npm 7 is now generally available! - The GitHub Blog
We're announcing version 7 of the npm CLI is now generally available. ... which is backwards compatible with npm 6 users.
Read more >Npm 7 is now the standard, here is what you'll get
The new lock file should be backwards compatible with users of npm 6. Though, when you run npm install in a project with...
Read more >Npm 7 Now Generally Available, Supports Workspaces and ...
npm 7's CLI now supports workspaces, i.e. supports managing multiple packages from within a singular top-level, root package. The workspaces ...
Read more >Node 14 and npm 7 upgrade gotchas - Mehul Kar
This is also backwards compatible with npm@6 , because it's a more deterministic way of getting the same behavior we already had.
Read more >What's new in npm v7 - LogRocket Blog
Learn about the new features part of the npm v7 release, including workspaces and auto-installed peer dependencies.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sounds like maybe a npm7 compatibility issue?
@kokiebisu in the meantime you can manually build your storybook and then run
chromatic
with the-d
(or--storybook-build-dir
) flag pointing to the build storybook directory.I think this was fixed with https://github.com/chromaui/chromatic-cli/pull/237