Ditch colors, use chalk?
Open
Nobody has claimed this yet.
refactoring
- Dominant language
- JavaScript
- Stars
- 806
- Forks
- 434
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 32
Description
Given what happened in:
https://github.com/w3c/respec/issues/3951
And it seems the author is unrepentant, we should probably move to chalk or some other lib.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue 3951 and identifying where Respec currently handles terminal colors; the issue does not name a file or test. Compare chalk with the proposed alternatives, then define the migration scope and verify that existing color output remains correct after the replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100