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 🙏

© 2024 – Pkg Stats / Ryan Hefner

global-modules-path

v3.0.0

Published

Returns path to globally installed package

Downloads

240,221

Readme

global-modules-path

Returns path to globally installed package.

System requirements

In order to use this package you need:

  • Node.js 4.0.0 or later
  • npm 2.0.0 or later added to your PATH environment variable (you should be able to execute npm --version from your default terminal).

Usage

The module has a single public method called getPath. It requires at least one argument - the name of the globally installed package that you need. In case the package is not installed, getPath will return null. getPath will throw error in case the OS is NOT supported. Supported OS are:

  • Windows (process.platform returns win32)
  • macOS (process.platform returns darwin)
  • Linux (process.platform returns linux)

Using getPath with single argument

Example:

let pathToPackage = require("global-modules-path").getPath("packageName");

The method returns the path to globally installed package or null. The code constructs the path based on the result of npm config get prefix and checks if the package exists.

Using getPath with package name and executable name.

Example:

let pathToPackage = require("global-modules-path").getPath("packageName", "executableName");

The method returns the path to globally installed package or null. The code constructs the path based on the result of npm config get prefix and checks if the package exists. In case the package cannot be found in this way, the executableName is used to determine if the package is globally installed.

  • On Windows the package spawns where executableName command and parses the result.
  • On macOS and Linux the package spawns ls -l executableName and which executableName and parses the results.

NOTE: In some cases the executable name is not the same as the package name.