sillsdev / sillsdev/TheCombine
Suppress error messages in dev
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 10
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 9
Description
Follow-up to #3041
Previously with npm run frontend and npm start (both in dev), console errors threw a small error toast at the bottom of the screen. After switching to Parcel, the errors now block the whole screen. It's quite annoying, and a hinderance to testing things.
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 running npm run frontend and npm start in development mode and observe how Parcel reports console errors. Trace the development error handling from those entry points; done means errors no longer block the whole screen and are presented in the less intrusive way described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100