[BUG] When called with a --package foo@version, npx doesn't cache it
Opened this issue · 1 comments
kenotron commented
What / Why
When npx is invoked with --package foo@1.2.3, npx doesn't cache it (maybe there is a good reason for this, but I can't think of one)
When
When npx is invoked with --package foo@1.2.3
Where
any package
Current Behavior
foo@1.2.3 is not cached
Steps to Reproduce
simply run npx with --package with a @ version - do this more than once
Expected Behavior
You should see the 2nd time that npx does not try to install packages again (caching the first install)
References
Look here:
- https://github.com/npm/npx/blob/latest/index.js#L172
- also semantic of the conditonal had changed when comparing the yargs-parser vs the fastPathArgs:
stalniy commented
+1 for this feature! I can even look into fixing it if somebody from npm team approves this