-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Using --json
still produces ANSI sequences via stdout
#3941
Comments
mjesun
added a commit
that referenced
this issue
Jun 30, 2017
…led. Fixes #3941" (#3951) * Revert "fix typo in snapshot testing documentation (#3948)" This reverts commit d6998c2. * Revert "Fix linting (#3946)" This reverts commit 9426521. * Revert "Avoid writing to stdout in default reporter if --json is enabled. Fixes #3941 (#3945)" This reverts commit 68d747d.
tushardhole
pushed a commit
to tushardhole/jest
that referenced
this issue
Aug 21, 2017
tushardhole
pushed a commit
to tushardhole/jest
that referenced
this issue
Aug 21, 2017
…led. Fixes jestjs#3941" (jestjs#3951) * Revert "fix typo in snapshot testing documentation (jestjs#3948)" This reverts commit d6998c2. * Revert "Fix linting (jestjs#3946)" This reverts commit 9426521. * Revert "Avoid writing to stdout in default reporter if --json is enabled. Fixes jestjs#3941 (jestjs#3945)" This reverts commit 68d747d.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As per the documentation, using the
--json
option when running Jest should divert all informative stuff tostderr
, then just leave the cream of the crop (i.e. the JSON) into stdout. However, when using--json
and piping to a file, I can still see ANSI escape sequences on the file:This causes pipe commands, like
jest --json my-test | jq .
, to fail.The text was updated successfully, but these errors were encountered: