jprichardson / jprichardson/node-suppose
Errors no longer caught
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 255
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Before, I would console.error(error); process.exitCode = 1 and the "error" event would be emitted. This is no longer happening now that I'm not using v0.6.2 from npm
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
Start by reproducing the missing error event and compare the current behavior with the npm v0.6.2 behavior described in the issue. Read the referenced node-pty issue for context; done means errors are logged, process.exitCode is set to 1, and the "error" event is emitted again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100