NPM Errors should not _just_ have process exited with status code 1
Open
@bryanmacfarlane is already working on this.
Since Mar 31, 2020.
enhancement
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 1.7k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Description
Errors from npm should ideally be highlighted and / or become a problem matcher
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.
Assessment
This issue has not been assessed yet.