Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] npm v6 windows install with prefix #3887

Closed
Xesenix opened this issue Oct 13, 2021 · 1 comment
Closed

[BUG] npm v6 windows install with prefix #3887

Xesenix opened this issue Oct 13, 2021 · 1 comment
Labels
Release 6.x work is associated with a specific npm 6 release

Comments

@Xesenix
Copy link

Xesenix commented Oct 13, 2021

As I didn't find an existing issue for this problem here is its description:

Current behavior

When running npm i --prefix project on Windows with node 14 and npm 6.14 install results in a lot of files created inside the project path. This problem doesn't appear on MAC or Linux versions or on Windows node 15 npm 7

Log after running command:

root\project\is-docker -> root\project\node_modules\is-docker\cli.js
root\project\mkdirp -> root\project\node_modules\mkdirp\bin\cmd.js
root\project\nopt -> root\project\node_modules\nopt\bin\nopt.js
root\project\installed-package-contents -> root\project\node_modules\@npmcli\installed-package-contents\index.js
root\project\sshpk-conv -> root\project\node_modules\sshpk\bin\sshpk-conv
root\project\sshpk-sign -> root\project\node_modules\sshpk\bin\sshpk-sign
...

Results in a lot of files where they shouldn't be:
obraz

Expected behavior

I assume those installed files should be inside project/node_modules/.bin but I am not sure about it.

Steps To Reproduce:

  1. create folder structure:
root
- project
  1. run npm init on root and root/project
  2. add some dependencies in project for example npm i @angular/cli
  3. remove node_modules - simulate as the whole project would be cloned from the repository
  4. try running npm i --prefix project from root folder

Environment

  • OS: Windows 10
  • Node: 14.17.4
  • npm: 6.14.14
@ljharb ljharb added the Release 6.x work is associated with a specific npm 6 release label Oct 13, 2021
@ruyadorno
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Release 6.x work is associated with a specific npm 6 release
Projects
None yet
Development

No branches or pull requests

3 participants