Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad advice when using npx #112

Open
tamzinblake opened this issue Jun 12, 2017 · 2 comments
Open

Bad advice when using npx #112

tamzinblake opened this issue Jun 12, 2017 · 2 comments

Comments

@tamzinblake
Copy link

tamzinblake commented Jun 12, 2017

In this example, npx is using the locally-installed version of bower (node_modules/.bin/bower). update-notifier is correctly noticing that we're not using the latest version, but it suggests that npm i -g bower will fix that, which it will not, since it'll still use the locally-installed version, which is old.

pasted image at 2017_06_12 03_26 pm

=> $ npm -v
5.0.3
=> $ node -v
v6.9.5
=> $ npx -v
4.0.3
@sindresorhus
Copy link
Member

I think we should make the isGlobal option default to auto-detecting whether it's installed globally or locally. Right now you have to set it manually. Can use the is-installed-globally package. Pull request welcome.

@tamzinblake
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants