Doctor complains when installation is not global

[dfee]

I want to install yeoman in my monorepo project... and wrap it as part of another tool (that registers the package elsewhere in the monorepo). however, this seems to annoy the doctor:

Yeoman Doctor
Running sanity checks on your system

✔ No .bowerrc file in home directory
✔ Global configuration file is valid
✖ NODE_PATH matches the npm root

Unable to find the npm root, something went wrong.
Try to execute npm -g root --silent on your command-line

✔ No .yo-rc.json file in home directory
✔ Node.js version
✔ npm version
✔ yo version

Found potential issues on your machine :(
npm WARN [email protected] No description
npm WARN [email protected] No repository field.

+ [email protected]
added 684 packages from 392 contributors and audited 4310 packages in 18.171s

19 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Is this verify necessary / useful? Can it be updated to support non-global installs?

doctor/lib/rules/node-path.js

Lines 43 to 62 in df93f8a

	exports.verify = async () => {
	if (process.env.NODE_PATH === undefined) {
	return null;
	}
	const nodePaths = (process.env.NODE_PATH || '').split(path.delimiter).map(fixPath);
	try {
	const stdout = childProcess.execSync('npm -g root --silent');
	const npmRoot = fixPath(stdout);
	if (nodePaths.indexOf(npmRoot) < 0) {
	return errors.pathMismatch(npmRoot);
	}
	return null;
	} catch (error) {
	return errors.npmFailure();
	}
	};

[SBoudrias]

It's useful for most users as it usually point to misconfigurations.

These are just warning, feel free to ignore if you know you have a special setup that is working fine.

[mshima]

@dfee if you are doing some custom lookups, you can consider using yeoman-environment directly.
AFAIC yo is a stand-alone cli and yeoman-doctor is an yo utility.