Skip to content
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.

Possible npm 3 issue #125

Open
sagivf opened this issue Nov 17, 2015 · 1 comment
Open

Possible npm 3 issue #125

sagivf opened this issue Nov 17, 2015 · 1 comment

Comments

@sagivf
Copy link

sagivf commented Nov 17, 2015

I have noticed a wired behaviour.

I published a simple module (lets call it "x") with one dependancy("bunyan") to my companies dedicated registry.
I installed it in a project.

If I publish a patch to "x" and run npm update on my project it updates but it installs bunyan inside the "x" node_modules and removes it from my projects node_modules which I need.
If i run npm install it reinstalls "bunyan" in the projects root node_modules but downgrades "x" to the previous version prior to the patch.
The solution seems to be: uninstall "x" and install again. then all is well.
Am I missing something?

@sagivf
Copy link
Author

sagivf commented Nov 20, 2015

Is this in the correct repo?

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

No branches or pull requests

1 participant