A problem with an installation via NPM

[klimcode]

Hi.
I don't know where to write about this problem. Hope, you know how to solve it.
I try to install "detect-port-alt" via NMP but it fails always.
No another package has this problem.

21645 verbose stack Error: ENOENT: no such file or directory, chmod '/mnt/storage/all/work/libraries/benchmark-react/node_modules/detect-port-alt/bin/detect-port'
21646 verbose cwd /mnt/storage/all/work/libraries/benchmark-react
21647 verbose Linux 4.13.0-36-generic
21648 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
21649 verbose node v9.2.0
21650 verbose npm  v5.7.1
21651 error path /mnt/storage/all/work/libraries/benchmark-react/node_modules/detect-port-alt/bin/detect-port
21652 error code ENOENT
21653 error errno -2
21654 error syscall chmod
21655 error enoent ENOENT: no such file or directory, chmod '/mnt/storage/all/work/libraries/benchmark-react/node_modules/detect-port-alt/bin/detect-port'
21656 error enoent This is related to npm not being able to find a file.
21657 verbose exit [ -2, true ]

[denghongcai]

npm/npm#9633 seems related to this issue?

[jkriss]

I'm seeing the same thing on Ubuntu 16.04 (node 9.8.0 and npm 5.6.0) although it works fine on Mac OS (node 9.7.1 and npm 5.6.0).

[klimcode]

The problem does not appear with Yarn. So, I have to use it with create-react-app.

[rajohns08]

I'm seeing the same issue on linux

[vinothvk]

Issue seems to be happening because of the two bin links pointing to the same file. For some reason this fails in nfs mounted drives. If we remove one of the bin link in package.json and install the package it works fine. I think it is an issue with npm or the bin-links node modules it uses or the nfs itself. Time being can the author of this module remove one of the bin link and publish new version? Or I can create a PR if you can publish that version.

[ketysek]

Also seeing the issue in node:8 docker image.

[0xc0d3r]

Hey! I'm using https://github.com/zeit/serve library and it has a dependency on detect-port lib. I'm also getting the error in only docker image and my node version is v8.11.3 as said by @ketysek. Did anyone solve the problem?

[ketysek]

@0xc0d3r yes, I've switched to yarn.

[snackCake]

I'm also seeing this problem after running create-react-app and running in Docker (node:8.11.3).

[abdelbolanos-cbc]

Hi, I just have the same issue in node 8.9.4 and I notice that my package-lock.json was causing it. Try to remove it (or rename it) and try again npm install. Good luck!!!

[stratease]

I'd recommend trying npm i --no-bin-links - this fixed our situation.

[zearg]

I'd this bug.
Solved : Be sure there is no package-lock.json in folder you type the command

[stewartmatheson]

I'd this bug.
Solved : Be sure there is no package-lock.json in folder you type the command

I tried this and got the same issue. Regardless I'm not sure some people can simply delete their package lock file as it may break some compatibility between other modules.

[aade-sh]

I think this has something to do with the file system in which it is being installed. I switched from my Windows ntfs to Linux ext4 and the installation went smoothly.