microsoft / microsoft/TypeScript
Improve TypeScript experience when dependencies are missing.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
I was in a project, and forgot that I deleted node_modules (or forgot to npm install), and in this case I was seeing any all over the place, and was jumping myself to conclusions that something was wrong with TypeScript or VS Code.
It could be helpful if VS Code could suggest something like
Did you forget to install dependencies? Perhaps you should run
npm install?
or similar.
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.
Research direction
The issue names no files or tests. Start by locating how missing dependencies affect type resolution and where diagnostics are surfaced, then confirm the proposed guidance with maintainers. Done means projects missing installed dependencies receive a clear install suggestion instead of misleading any results, with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- compilers, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100