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
Let I have a package-a(version 1.0.0) and another package-b(version 1.0.0). package-a depends on package-b by ^1.0.0.
Now if we run npm install on the root folder. Everything works fine. The node_modules of the root contain both package-a(version 1.0.0) and package-b(version 1.0.0).
But now if we update package b to version 2.0.0, package-a breaks. Because it doesn't find its dependency(package-a@^1.0.0).
The intended behavior would be package-a containing the version 1.0.0 of package-b in its node_modules folder. But it doesn't happen. How to make it happen?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Let I have a package-a(version 1.0.0) and another package-b(version 1.0.0). package-a depends on package-b by ^1.0.0.
Now if we run
npm install
on the root folder. Everything works fine. The node_modules of the root contain both package-a(version 1.0.0) and package-b(version 1.0.0).But now if we update package b to version 2.0.0, package-a breaks. Because it doesn't find its dependency(package-a@^1.0.0).
The intended behavior would be package-a containing the version 1.0.0 of package-b in its node_modules folder. But it doesn't happen. How to make it happen?
Beta Was this translation helpful? Give feedback.
All reactions