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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow code frame to be disabled on console.log #9877

Closed
mike-dazn opened this issue Apr 24, 2020 · 3 comments
Closed

Allow code frame to be disabled on console.log #9877

mike-dazn opened this issue Apr 24, 2020 · 3 comments

Comments

@mike-dazn
Copy link

馃殌 Feature Proposal

Under #9741 all logs from console.log are wrapped in a frame. This has added a lot of visual noise to some builds we have which log progress of some polling tests.

Some sort of config or flag to make it behave like it did in 0.25.3. This was discussed in #9741 but was ultimately not implemented #9741 (comment)

This is how it used to look in 0.25.3:

Found 0 messages out of an expected 1. Attempt #8. Polling since 7.7s ago.
Found 0 messages out of an expected 1. Attempt #9. Polling since 8.7s ago.

And now how it looks in 0.25.4:

  console.log
    Found 0 messages out of an expected 1. Attempt #8. Polling since 7.7s ago.

      at Object.invoke (node_modules/<snip>/index.js:71:11)

  console.log
    Found 0 messages out of an expected 1. Attempt #9. Polling since 8.7s ago.

      at Object.invoke (node_modules/<snip>/index.js:71:11)

Motivation

I'd like the ability to have console.log behave the same way I did in 0.25.3

Example

See above

Pitch

@github-actions
Copy link

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the Stale label Feb 25, 2022
@github-actions
Copy link

This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

@github-actions
Copy link

github-actions bot commented May 4, 2022

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 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant