search

chromaui / chromatic-cli

Chromatic CLI: `npx chromatic`
https://www.chromatic.com/docs/cli
MIT License
289 stars 72 forks source link

TurboSnap disabled until base directory is set correctly #1031

Open KyneSilverhide opened 2 months ago

KyneSilverhide commented 2 months ago

Since we updated storybook and chromatic, we now have this issue each time we try to publish to chromatic (from CICD or from our own development laptops)

              × TurboSnap disabled until base directory is set correctly
              The base directory allows TurboSnap to trace files.
              Set the --storybook-base-dir option as the relative path from the repository root to the Storybook project root.
              Run @chromatic-com/turbosnap-helper to get your base directory value.
12:14:25.927  i Wrote Chromatic diagnostics report to chromatic-diagnostics.json

The settings IS set in the command line.. "chromatic": "npx chromatic --project-token=XXXXXXX --exit-zero-on-changes --storybook-base-dir=libs/care-common-lib/.storybook --build-script-name=build-storybook-lib"

I also tried to put the values in chromatic.config.json, but the issue persists (this solution was found on other similar issues)

{
  "onlyChanged": true,
  "projectId": "...",
  "storybookConfigDir": "./libs/care-common-lib/.storybook",
  "storybookBaseDir": "./libs/care-common-lib/.storybook",
  "zip": true
}

Versions used :

   "chromatic": "11.7.1",
   "@chromatic-com/storybook": "1.8.0",
   "@nx/storybook": "18.2.4",

Setting onlyChanged to false is our current workaround.

alextrukhan commented 1 month ago

Any suggestions how to fix this? or idea what is the root cause? @KyneSilverhide have you managed to fix the issue? we have same error but only on CI, on dev machines everything workd