You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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 theproject
path. This problem doesn't appear on MAC or Linux versions or on Windows node 15 npm 7Log after running command:
Results in a lot of files where they shouldn't be:

Expected behavior
I assume those installed files should be inside
project/node_modules/.bin
but I am not sure about it.Steps To Reproduce:
npm init
onroot
androot/project
project
for examplenpm i @angular/cli
node_modules
- simulate as the whole project would be cloned from the repositorynpm i --prefix project
from root folderEnvironment
The text was updated successfully, but these errors were encountered: