Error message: Failed to collect Storybook metadata
See original GitHub issueError: ✖ Failed to collect Storybook metadata
Could not find a supported Storybook viewlayer package. Make sure one is installed, or set CHROMATIC_STORYBOOK_VERSION.
at...
Users often get this message because Storybook is not installed as a dependency in their environment. This can happen in CI or locally if they’ve just cloned the project.
Strawman Be more direct about a possible solution.
Error: ✖ Failed to collect Storybook metadata
Could not find a supported Storybook view layer package. This can happen if the dependency hasn't been installed in your environment yet. Run `npm install` or `yarn` to make sure Storybook is installed.
If Storybook is installed, you can also set CHROMATIC_STORYBOOK_VERSION.
at...
┆Issue is synchronized with this Asana task by Unito
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
building your Storybook fails (only with chromatic) #227 - GitHub
If I run the failed command npm run --silent build-storybook -- --output-dir ... Collected Storybook metadata → Storybook v6.1.11 for Vue; ...
Read more >Chromatic deployment error when using github-actions
Error: ✖ Failed to collect Storybook metadata Could not find a supported Storybook viewlayer package. Make sure one is installed, or set ...
Read more >Publish Storybook
Storybook is a frontend workshop for building UI components and pages in isolation. Thousands of teams use it for UI development, testing, and...
Read more >How to Troubleshoot an Incorrect Deployment
xml but not found in Zipped directory" error. Deployment completed successfully but some components, profile permissions or code was not ...
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
Released 5.8.1 which reverts to something similar to the earlier behaviour, please try it out.
@domyen just wanted to give you a heads up that is also seems to happen if you use yarn v1 workspaces and install packages at the workspace root, rather than in individual projects (which isn’t exactly a great practice, but can be convenient for projects that use create-react-app).
the workaround is to list your current version of storybook as a dependency or devdependency in the project itself, but it’d be lovely if it worked w/o having to do this (as it did a month or so ago)