microsoft / microsoft/TypeScript
Suggestion: Better error message when unable to resolve modules
Open
@DanielRosenwasser is already working on this.
Since May 5, 2016.
Docs
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Related to our woes with #8189, if the compilation errors gave some better hinting when it was unable to resolve a module, we might not have taken so long to find the solution (and we wouldn't have filed an issue!).
The idea would be that if there is a compilation error of cannot file module "whatever", to make some intelligent checks against the parameters the compilation is running under and suggest using --moduleResolution node if the user is not already doing so.
Contributor guide
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.
Assessment
This issue has not been assessed yet.