Runtime: Add fine grained linker errors
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Right now I'm throwing some general errors in the linker if imports go wrong. These are quite broad errors
It would be nice to throw really fine-grained errors: like the module isn't at the path that it's been mapped to, or it's not in the repo, or whatever.
This requires really close testing and a bit of re-working of the module loader code - which is fine but not that conducive to nice clean errors.
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 locating the runtime linker and module loader code, then trace where broad import errors are currently thrown. Review the existing loader tests and add coverage for each reported failure case; done means imports produce distinct, accurate errors for missing mapped paths, absent modules, and other identified failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100