Update Karma to latest, make errors more helpful
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
See if newer Karma makes error reporting better (it currently omits stack traces in some cases, which requires going on a bug hunting safari each time). See https://github.com/karma-runner/karma/issues/3296
To test a difficult-to-debug error, checkout commit bc435fcef9320f4c20c9802f94ef71f7667cef87 of the lume/lume repo (recursively including sub modules).
Also see the try-to-improve-error-output branch here in cli, to see if we can improve the console logging.
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 checking the try-to-improve-error-output branch in cli and reviewing the linked Karma issue. Reproduce the difficult-to-debug error by checking out lume/lume commit bc435fcef9320f4c20c9802f94ef71f7667cef87 with its submodules, then compare current output with the branch. Done means updating Karma if it improves reporting and making console errors include useful stack traces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100