stderr from the target is not piped with correct color
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 816
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
stderr from the target is not piped with correct color. For example we have a target that runs webpack devserver which outputs errors however it is not meant to exit. We use lage so we can run ^build a head of starting the devserver.
To Reproduce
Steps to reproduce the behavior:
- Create a target that logs to
stderrbut exits with 0 - Run that target with
--verbose - Observe the output,
stderrmessage will be greyed out.
Expected behavior
A clear and concise description of what you expected to happen.
Environment/Troubleshooting
Please paste in the result of npx envinfo to help identify your run time environment
If this is an issue with run order of tasks, please paste in the result of lage info [your command(s)] [options]
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the issue with a target that writes to stderr and exits with 0, then run it with --verbose and inspect the output handling. Trace the verbose task-output path responsible for coloring stderr, and add or update a regression test if the relevant test location is identified; done means stderr retains its correct color.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100