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

Side effects on native dependencies on Windows #54

Open
malipetek opened this issue Sep 17, 2018 · 1 comment
Open

Side effects on native dependencies on Windows #54

malipetek opened this issue Sep 17, 2018 · 1 comment

Comments

@malipetek
Copy link

Havent got time to inspect really but this was quite annoying. After installing and including module. Scripts with native dependencies started not responding. Also some regular npm modules went missing.

Even after rebuilding and reinstalling Node, this effect continues. Any assumption would be appreciated. How come some package can be installed with npm but not rebuilding or not uninstalling with npm?

@ericblade
Copy link

Not sure if related, but whenever I execute a "npm install --save (new-module-to-install)" in a project folder on Windows, all the other modules that weren't the one i installed get nuked. Using npm 6.0.0. I have to follow with a regular npm install to reinstall all the other modules that disappeared.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants