deps mis-alignment: avoid `npm i` while another `npm i` is in progress
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 17
Description
I believe that even though a previous npm i is auto-magically running in the background
the current implementation could trigger another npm i without waiting for the first one to terminate.
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 file, test, or entry point. Start by locating the TypeScript code that launches the automatic npm i in this VSCode extension, then trace whether a second install can begin before the first terminates. Done means concurrent npm i processes are prevented and the behavior is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100