jaredhanson / jaredhanson/electrolyte
Better error handling on requiring component
- Dominant language
- JavaScript
- Stars
- 555
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
If for some reasons script can't be initialized you just drop that error [here](https://github.com/jaredhanson/electrolyte/blob/v0.3.0/lib/container.js#L126).
That information would be super useful for debug. Could you fix that and show that error stack in addition to [this error message](https://github.com/jaredhanson/electrolyte/blob/v0.3.0/lib/container.js#L133)?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in lib/container.js at the error handling around lines 126 and 133. Trace how component initialization failures are caught, then ensure the original error stack is shown alongside the existing error message. Done means initialization failures retain their debugging stack information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100