-
-
Notifications
You must be signed in to change notification settings - Fork 132
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
Should isGlobal work with npm link? #139
Comments
pofallon
changed the title
isGlobal behavior inconsistent with README
Should isGlobal work with npm link?
Apr 22, 2018
It will work fine when you publish, so I don't really see this as an issue worth caring about, but if anyone wants to do a PR to properly detect it, I'm fine with that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm currently developing a CLI that I've linked with
npm link .
in order to execute it as if it's globally installed (while I'm still working on it). However, executing it this way doesn't seem to trigger the "isGlobal" setting (I still have to explicitly set it totrue
to get "-g" to show up in the upgrade message). I suppose this won't matter once it's released to npm and people have actually installed it globally, but I was wondering if this is expected behavior. Should I expect isGlobal to default totrue
when I've simplynpm link
-ed it during development? Thanks!The text was updated successfully, but these errors were encountered: