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

Using --json still produces ANSI sequences via stdout #3941

Closed
mjesun opened this issue Jun 29, 2017 · 1 comment
Closed

Using --json still produces ANSI sequences via stdout #3941

mjesun opened this issue Jun 29, 2017 · 1 comment
Assignees

Comments

@mjesun
Copy link
Contributor

mjesun commented Jun 29, 2017

As per the documentation, using the --json option when running Jest should divert all informative stuff to stderr, 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:

ANSI escape sequences

This causes pipe commands, like jest --json my-test | jq ., to fail.

@cpojer cpojer closed this as completed in 68d747d Jun 30, 2017
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
…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.
@github-actions
Copy link

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant