Errors in hooks are swallowed
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3k
- Forks
- 101
- PR merge metrics
- No merged PRs in 30d
Description
Is there a reason hook errors aren't exposed to the user? We go straight from try to finally:
https://github.com/lukeed/uvu/blob/e419ff993b03094d61c2a29a3c8874b1dea929e1/src/index.js#L88
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 at src/index.js around line 88, using the linked revision to inspect how hook execution moves from try to finally. Reproduce a failing hook and trace whether its error reaches the user; done means hook errors are no longer silently swallowed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100