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
The versions (foo@1.0.0) aren't necessary in this form (npm i foo bar baz...), because npm recognizes they are in the package.json and uses the version range specified there. In other words, if "glob": "^6.0.0" is specified in dependencies, npm i glob will always install glob@^6.0.0.
As for speed, the only gains I can think of would be the omission of the dependencies unique to the local packages, and those are probably minimal at best. Regardless, this sounds like a good way to fix #59. I'll take a crack at it later today.
This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.
lockbot
locked as resolved and limited conversation to collaborators
Dec 28, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now we're just executing
npm install
in each package directory. However, because of the "linked" dependencies, we have an order of operations issue, either we end up installing over the linked dependencies or we try installing dependencies that do not exist.A possible solution to this might be manually writing out what we want to install:
This might fix #59. Also I wonder if this will make npm any faster because we're explicitly asking it for things, probably not, but maybe.
The text was updated successfully, but these errors were encountered: