GitHub action failing with "Storybook package not installed"
See original GitHub issueWith the release of Chromatic CLI v6.0.0 all our GitHub actions using the chromaui/action@v1
are now failing with the following error:
Chromatic CLI v6.0.0
https://www.chromatic.com/docs/cli
Authenticating with Chromatic
→ Connecting to https://index.chromatic.com
Could not retrieve package info from registry; skipping update check
Authenticated with Chromatic
→ Using project token '*'
Retrieving git information
Retrieved git information
→ Commit '*******' on branch 'main'; found 2 parent commits
Collecting Storybook metadata
→ ✖ Storybook package not installed
Could not find @storybook/react in node_modules.
Most likely, you forgot to run npm install or yarn before running Chromatic.
✖ Failed to collect Storybook metadata
✖ Storybook package not installed
Could not find @storybook/react in node_modules.
Most likely, you forgot to run npm install or yarn before running Chromatic.
→ View the full stacktrace below
If you need help, please chat with us at https://www.chromatic.com/docs/cli for the fastest response.
You can also email the team at support@chromatic.com if chat is not an option.
Please provide us with the above CLI output and the following info:
{
"timestamp": "2021-09-30T13:35:28.504Z",
"sessionId": "102360cb-5060-471a-82bd-1600fb5a5512",
"gitVersion": "2.33.0",
"nodePlatform": "linux",
"nodeVersion": "12.13.1",
"packageName": "chromatic",
"packageVersion": "6.0.0",
"flags": {
"projectToken": "***",
"workingDir": "packages/console-frontend",
"fromCI": true,
"interactive": false,
"exitZeroOnChanges": true,
"exitOnceUploaded": true,
"allowConsoleErrors": false
},
"buildScript": "build-storybook -s public",
"errorType": "Error",
"errorMessage": "✖ Failed to collect Storybook metadata"
}
This is happening across all our builds now with no code changes to the action/package.json/or lock file in our code so appears to be completely isolated to the action itself.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:11
- Comments:15 (6 by maintainers)
Top Results From Across the Web
New storybook v6.4.22 version is failing in Github Action env
Tried to upgrade to v6.4.22 and suddenly the CI environment in Github Actions started breaking. The versions that were bumped from -> to ......
Read more >Using Github Actions Fails to Deploy Storybook to Github Pages
... Storybook on: push: branches: - master jobs: build-and-deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: Install ...
Read more >Setup • Chromatic docs
Learn how to setup Chromatic and publish Storybook. ... Once you installed the chromatic package and have a <project-token> , run the following...
Read more >chromatic - npm
You can use this package normally, which means installing it and adding a script ... Do not run this based on a github...
Read more >Error installing R packages in GitHub actions: `Unable to ...
I'm trying to render a book via bookdown using GitHub Actions. The package dependencies install correctly when I use the following line: ...
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
Hey all Dominic from Chromatic here:
We reverted the latest package
6.0.0
back to5.10.2
. That should unblock you while we debug further.npx
this should also resolve any issues.6.0.0
you’ll have to reset it to5.10.2
Let me know if that works for y’all here or via our in-app chat (faster response).
https://github.com/tobilen/chromatic-repro
checkout run yarn run
npx chromatic -t xxx
tell me if you need the project token, i’ll send it via chromatics intercom