npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

win-user-installed-npm-cli-path

v4.0.0

Published

Resolve the path of `npm-cli.js` included in the user-installed npm on Windows

Downloads

2,503

Readme

win-user-installed-npm-cli-path

npm version Build Status Build status Coverage Status

Resolve the path of npm-cli.js included in user-installed npm on Windows

const winUserInstalledNpmCliPath = require('win-user-installed-npm-cli-path');

(async () => {
  const cliPath = await winUserInstalledNpmCliPath();
  //=> 'C:\\Users\\me\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js'
  });
})();

Installation

Use npm.

npm install win-user-installed-npm-cli-path

API

const winUserInstalledNpmCliPath = require('win-user-installed-npm-cli-path');

winUserInstalledNpmCliPath()

Return: Promise<string>

It resolves the path of npm-cli.js included in the user-installed npm CLI on Windows. "User-installed" means that it has been installed with npm install --global npm command by the user, and it might be located on the path different from where the default Node.js-bundled npm has been installed.

It uses global prefix config as a base path for searching npm CLI location.

// npm config set prefix tmp --global

(async () => {
  await winUserInstalledNpmCliPath();
  //=> 'C:\projects\your_project\tmp\node_modules\npm\bin\npm-cli.js'
})();

For POSIX

Use real-executable-path instead.

const realExecutablePath = require('real-executable-path');

(async () => {
  await realExecutablePath('npm');
  //=> '/usr/local/lib/node_modules/npm/bin/npm-cli.js'
})();

License

ISC License © 2017 - 2019 Watanabe Shinnosuke