[BUG] npm creates unnecessary bin folder on 2nd install
Open
Nobody has claimed this yet.
Bug
Priority 2
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
rm -rf _delme
mkdir _delme
cd _delme
$ ### First RUN ###
$ npm install typescript --no-bin-links && dir -1a node_modules/
added 1 package in 2s
.
..
.package-lock.json
typescript
$ ### Second RUN ###
$ npm install typescript --no-bin-links && dir -1a node_modules/
changed 1 package, and audited 2 packages in 2s
found 0 vulnerabilities
.
..
.bin
.package-lock.json
typescript
The .bin folder should not be there
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
Reproduce the issue by running the two npm install commands in the report with --no-bin-links and inspecting node_modules after each run. Trace the npm install path that creates .bin on the second run, then verify that the folder is absent after both installs while the typescript package remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100