Request: Better debugging of config
Open
Nobody has claimed this yet.
🎨 Type: Enhancement
🛠 Type: Feature Request
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
Related: https://github.com/zeit/hyperterm/issues/502
It's very hard to track down issues in the CSS/config with a generic alert.
Perhaps the error stack trace could be sent to stdout or to the console in DevTools?
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
Read related issue #502 and locate the code path that produces the generic alert for CSS or config errors. Determine how the error stack trace could be exposed through stdout or DevTools, then verify that the resulting diagnostics are visible when such an error occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100