[BUG] npm creates unnecessary bin folder on 2nd install

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

This is not a regression, same thing happens with node v20.0.0 (includes npm 9.6.4)

Not able to reproduce with the steps...

root@c859934a858b:/test# uname -s
Linux
root@c859934a858b:/test# npm -v
11.4.2
root@c859934a858b:/test# node -v
v22.17.0
root@c859934a858b:/test# npm install typescript --prefix ./_delme --global --no-bin-links

added 1 package in 399ms
root@c859934a858b:/test# ls
_delme
root@c859934a858b:/test# dir -1a ./_delme
.
..
lib

@milaninfy

@milaninfy
the first time npm install is run, there is no bin folder
the second time npm install is run, there is a bin folder

Just edited the issue post since it was confusing

Navigation Menu

Repository navigation

[BUG] npm creates unnecessary bin folder on 2nd install #8409

Is there an existing issue for this?

This issue exists in the latest npm version

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[BUG] npm creates unnecessary bin folder on 2nd install #8409

Description

Is there an existing issue for this?

This issue exists in the latest npm version

Activity

alexsch01 commented on Jul 1, 2025

milaninfy commented on Jul 15, 2025

alexsch01 commented on Jul 15, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions