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
{{ message }}
This repository has been archived by the owner on Jul 6, 2019. It is now read-only.
The description for the flag --no-install says: Skip installation if a package is missing.
How about skipping installation even if the package exists (And maybe bind that behaviour to another flag)? When you run npx <some-package> the NPM registry will always be queried for a newer release. When you repeatedly execute CLI commands you don't want to do that.
It'd be much nicer to say: npx --no-install <some-package> than node_modules/.bin/<some-package> or even $HOME/.node_modules/.bin/<some-package> (You can run npx anywhere, regardless if there's node_modules in your cwd or not).
The description for the flag
--no-installsays:Skip installation if a package is missing.How about skipping installation even if the package exists (And maybe bind that behaviour to another flag)? When you run
npx <some-package>the NPM registry will always be queried for a newer release. When you repeatedly execute CLI commands you don't want to do that.It'd be much nicer to say:
npx --no-install <some-package>thannode_modules/.bin/<some-package>or even$HOME/.node_modules/.bin/<some-package>(You can run npx anywhere, regardless if there's node_modules in your cwd or not).Also see #214
The text was updated successfully, but these errors were encountered: