question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Chromatic 5.6.2 Breaks in CircleCI

See original GitHub issue

Running V5.6.2 breaks on Circle CI with this script:

#!/bin/bash -eo pipefail
if [ "${CIRCLE_BRANCH}" != "main" ];
  then
    yarn chromatic --project-token=${CHROMATIC_PROJECT_TOKEN} --exit-zero-on-changes
else
  yarn chromatic --project-token=${CHROMATIC_PROJECT_TOKEN} --auto-accept-changes
fi

yarn run v1.22.4
$ npx chromatic --project-token ********** --project-token=********** --exit-zero-on-changes
Unhandled promise rejection: The flag --projectToken can only be set once.
Error: The flag --projectToken can only be set once.
    at validateFlags (/home/circleci/project/node_modules/chromatic/node_modules/meow/index.js:101:10)
    at meow (/home/circleci/project/node_modules/chromatic/node_modules/meow/index.js:213:2)
    at parseArgs (/home/circleci/project/node_modules/chromatic/bin/lib/parseArgs.js:4:39)
    at Proxy.main (/home/circleci/project/node_modules/chromatic/bin/main.js:32:67)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Exited with code exit status 1
CircleCI received exit code 1

Works fine on v5.5.0.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
ndelangencommented, Feb 17, 2021

I released 5.6.3 just now!

1reaction
tmeasdaycommented, Feb 17, 2021

@bodograumann this seems like a different issue to #235?

@hamatoyogi it looks like your package.json already sets the --project-token flag? So you could simplify your script to:

if [ "${CIRCLE_BRANCH}" != "main" ];
  then
    yarn chromatic --exit-zero-on-changes
else
  yarn chromatic --auto-accept-changes
fi
Read more comments on GitHub >

github_iconTop Results From Across the Web

Error while parsing cli flags · Issue #235 · chromaui/chromatic-cli
Since today all our chromatic builds have been failing with the following error: $ npx chromatic ... Chromatic 5.6.2 Breaks in CircleCI #281....
Read more >
Automate Chromatic with CircleCI • Chromatic docs
Builds that contain visual changes need to be verified. They will fail if you are not using --exit-zero-on-changes . Once you accept all...
Read more >
wave/chromatic - Orbs - CircleCI
Chromatic ensures consistency in UI components, down to the pixel. Every commit is automatically tested for visual changes in the cloud.
Read more >
Track CircleCI Updates
Track our platform changes and updates via the CircleCI Changelog. Stay up to date with the latest in Continuous Integration.
Read more >
CircleCI Release Notes
Prometheus is broken in KOTS versions 1.65.0 - 1.67.0. If you rely on this feature, do not upgrade your KOTS version until this...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found