WebStorm console, Windows Command Prompt do not support 256 colors

Open
#702 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
tooling

Research direction

No file or test is identified in the report. Start by reproducing the 256-color behavior in Windows Command Prompt and the WebStorm debug console, compare it with cmder, and determine whether completed work should restore usable 16-color output or provide a documented way to select it.

Written by the indexing model from the issue text.

Description

question

Just upgraded from 2.6.8 to 4.1.1. I'm on Windows. The 256 colors do not work well in some environments - for example, Windows Command Prompt and the WebStorm debug console. I just get white (or maybe it's light gray) for everything. The colors do work in cmder shell, but that's not enough. Is there a way to tell 4.1.1 to just use the 16 colors that the older version used? Or do I just need to stick with the old version?

Dominant language
JavaScript
Stars
11.5k
Forks
992
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from debug-js/debug

All issues in debug-js/debug

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.