Skip to content
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

Error when trying to run Chromatic #681

Closed
w3bdesign opened this issue Nov 22, 2022 · 3 comments
Closed

Error when trying to run Chromatic #681

w3bdesign opened this issue Nov 22, 2022 · 3 comments
Labels
bug Classification: Something isn't working needs triage Tracking: Issue needs confirmation

Comments

@w3bdesign
Copy link

Bug report

I have ran Chromatic without issues until today, when I started getting build errors in CircleCI.

I did a run today locally with the exact same command and in the same repo, with the command yarn chromatic --project-token=xxxxxxx

I tried both yarn and npx and got the same error.

For reference, here are my version numbers for Node and npm:

$ node --version
v18.12.0

$ npm --version
8.19.2

The error I get is this:

ERR! ModuleNotFoundError: Module not found: Error: Can't resolve 'C:\GitHub\dfweb-v3\storybook-init-framework-entry.js' in 'C:\GitHub\dfweb-v3'

@w3bdesign w3bdesign added bug Classification: Something isn't working needs triage Tracking: Issue needs confirmation labels Nov 22, 2022
@ghost
Copy link

ghost commented Nov 22, 2022

We started having issues today too when running in GitHub actions using chromaui/action@v1. You can see the entire error log here: https://github.com/mintlify/components/actions/runs/3526368423/jobs/5914214299

Publishing the Storybook from the CLI works (npx chromatic --project-token=redacted)

@kylegach
Copy link
Contributor

I believe this is an issue with Storybook and not Chromatic.

Unfortunately, a transitive dependency of Storybook released a new minor version that is incompatible with Storybook. We're working with the maintainers to come up with a solution, but in the meantime, you can pin the version to the last known working release:

npm (if on npm 8 or higher)

{ "overrides": { "enhanced-resolve": "5.10.0" } }

Yarn

{ "resolutions": { "enhanced-resolve": "5.10.0" } }

pnpm

{ "pnpm": { "overrides": { "enhanced-resolve": "5.10.0" } } }

Sorry for the hassle!

@w3bdesign
Copy link
Author

This fixed the issue for now, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Classification: Something isn't working needs triage Tracking: Issue needs confirmation
Projects
None yet
Development

No branches or pull requests

2 participants