Skip to content
This repository has been archived by the owner on Jul 6, 2019. It is now read-only.

use npm update instead of npm install on ~/.npm/_npx-globals #11

Closed
zkat opened this issue May 30, 2017 · 1 comment
Closed

use npm update instead of npm install on ~/.npm/_npx-globals #11

zkat opened this issue May 30, 2017 · 1 comment

Comments

@zkat
Copy link
Owner

zkat commented May 30, 2017

Right now, if you don't have a certain package in $PATH, we always do a npm install --global into $(npm config get cache)/_npx. This means that we'll run through an actual install cycle every time, instead of just making sure we're at the latest version.

So, we should use npm update instead, which should short-circuit this.

Unfortunately, npm is kinda wonky with npm update and globals right now, so we need to fix up npm update for this use case before we can take advantage of it.

@zkat
Copy link
Owner Author

zkat commented Jul 12, 2017

I'm gonna close this for now, because speeding up installs is going to be a bit more involved after some recent changes meant to isolate npx runs from each other. This should still be optimized, but I don't think it's the only (or best) way.

@zkat zkat closed this as completed Jul 12, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant