Should isGlobal work with npm link?

[pofallon]

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 to true 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 to true when I've simply npm link-ed it during development? Thanks!

[sindresorhus]

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.