Deps mis-alignment: after running `npm i` we cannot assume diagnostics can safely be cleared
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 17
Description
Perhaps the diagnostics should be re-calculated, but that carries the risk of entering
and infinite loop of npm i if the original issue is never resolved.
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 does not name a file, test, or entry point. Start by tracing the dependency-alignment diagnostics and the code that runs after npm i; define completion around recalculating diagnostics without repeatedly triggering npm i when the underlying issue remains unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100