console.log doesn't interpret %c format option.

[clozr]

When running in jest, the %c in console.logs are not properly handled and treated as just string. Therefore corresponding style argument is not correctly consumed leading to different console output. Any idea how to fix it.

[thymikee]

We're emulating console, and this may not work, but I hadn't check myself. Would you mind sending a PR with a fix? :)

[thymikee]

So I've had a look now and console features like %d or %s are working just fine with Jest. But FWIW, %c is not a part of Console in Node. Seems like this is only available in browsers, so I'd say it's a wontfix.

[clozr]

I know it is not a part of console in node. However, we use jest to test all kind of application such as react.js. Not just node.js application. So I would say it should be fixed. I can create a pull request.

…

On Feb 27, 2017, at 11:04 AM, Michał Pierzchała ***@***.***> wrote: So I've had a look now and console features like %d or %s are working just fine with Jest. But FWIW, %c is not a part of Console in Node. Seems like this is only available in browsers, so I'd say it's a wontfix. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3010 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANlTz2KeGPZZfkUB5e4MUwpmjlnZRtutks5rgx5WgaJpZM4MMgul>.

[clozr]

Thanks a lot for reopening. React/React-Native debugging uses lots of advanced console features. I will slowly start adding more to the console.log emulation...starting with %c support.

[cpojer]

This should be done in nodejs directly: nodejs/node#10308

[github-actions]

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.