You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chalk works perfect for nearly all use cases we have and we make heavy use of testing for chalk.enabled to decide how we format our log output. This works in the local command line as expected and logs are printed colorfully.
Since we're switching from Atom to VSCode I've noticed that the color mode detection doesn't seem to work for the VSCode console. chalk reports supportsColor and enabled both being false. The VSCode Debug Console clearly supports colors and if I manually enforce chalk to use colors it works fine and as expected. But I wonder if this automatic detection is something that can be fixed?
The text was updated successfully, but these errors were encountered:
Chalk works perfect for nearly all use cases we have and we make heavy use of testing for
chalk.enabled
to decide how we format our log output. This works in the local command line as expected and logs are printed colorfully.Since we're switching from Atom to VSCode I've noticed that the color mode detection doesn't seem to work for the VSCode console.
chalk
reportssupportsColor
andenabled
both being false. The VSCode Debug Console clearly supports colors and if I manually enforcechalk
to use colors it works fine and as expected. But I wonder if this automatic detection is something that can be fixed?The text was updated successfully, but these errors were encountered: