Detect if the CLI has been installed globally or as a dev dependency

[itaisteinherz]

When notified to update a CLI, the suggested command the user should run to update the CLI ignores the way the CLI has been installed, e.g. gloablly or as a dev dependency. The suggested command should be adjusted accordingly.

IssueHunt Summary

litomore has been rewarded.

Sponsors (Total: $40.00)

• issuehunt ($40.00)

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[sindresorhus]

This was already implemented for npm in 97d0b97. For Yarn, see #132.

[itaisteinherz]

This was already implemented for npm in 97d0b97. For Yarn, see #132.

97d0b97 and #132 only detect if the module has been installed globally, not if it was if it was installed as a dev dependency (or any other type of dependency).

I mostly encounter CLIs installed as either global or dev dependencies, and so I think dev dependency detection should be added.
Peer, optional and bundled dependencies are used sometimes but detecting those would probably be unnecessary (since CLIs aren't normally installed as such dependencies).

[IssueHuntBot]

@IssueHunt has funded $40.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[IssueHuntBot]

@sindresorhus has rewarded $36.00 to @LitoMore. See it on IssueHunt

• 💰 Total deposit: $40.00
• 🎉 Repository reward(0%): $0.00
• 🔧 Service fee(10%): $4.00