npm is suggested when installed via yarn (global install only)

[OmgImAlexis]

I have xo installed via yarn not npm which means if I "update" with npm I'll end up with two copies of xo in my $PATH.

➜  SickRage git:(develop) ✗ realpath $(which xo)      
/Users/xo/.config/yarn/global/node_modules/xo/cli.js

   ╭───────────────────────────────────────╮
   │                                       │
   │   Update available 0.17.1 → 0.18.2    │
   │       Run npm i -g xo to update       │
   │                                       │
   ╰───────────────────────────────────────╯

[sindresorhus]

Yarn users should IMHO know what to do when they see npm install instructions. Same with readmes, almost no projects document Yarn in the install instructions.

[OmgImAlexis]

Is there any harm in adding a check for it? Just checking if the path to the package contains yarn should be enough to determine if it's installed via yarn.

[SBoudrias]

@OmgImAlexis That's a good idea. I'm sure a PR is welcomed to fix that.

[LitoMore]

const updateNotifier = require('update-notifier');
const pkg = require('chalk/package');

const notifier = updateNotifier({pkg});

notifier.notify();

How to determine whether chalk is installed by npm or yarn?

[LitoMore]

I will make a pull request to solve the issue.