Enhancement proposal - stream stdout/stderr
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 262
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
From what it looks like in the source, the output of the command is only rendered to terminal after it is completely finished.
I'd like to use this package for running commands that have multiple steps and could take 30s+.
With no output to verify that the command is indeed running, it has a negative effect on developer experience.
Would you consider streaming the stdout or adding an option for this?
Thanks for the project!
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
The issue identifies the command output path in the source but names no file or test. Trace how command stdout and stderr are currently collected and rendered, then decide the intended streaming behavior or option semantics. Done means long-running, multi-step commands visibly emit output before completion, with coverage for the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100