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

npm-module-path

v2.0.2

Published

Local and global search module directory

Downloads

61

Readme

npm-module-path

Get the path of the given package(s) if it is installed globally or locally.

Travis Status AppVeyor status

Install

$ npm i -S npm-module-path

Why?

Primarily, this module is designed to search modules for VS Code (Language Server Extensions, etc).

  • Dependencies free.
  • Returns the path to the module directory (without require).
  • Can work with an array of dependencies.

Usage

const nmp = require('npm-module-path');

nmp.resolveOne('mocha').then((filepath) => {
	console.log(filepath); // ['/home/travis/.nvm/versions/node/v6.6.0/lib/node_modules/mocha']
});

nmp.resolveMany(['mocha', 'tslint']).then((filepaths) => {
	console.log(filepaths); // ['node_modules/mocha', '/usr/lib/node_modules/tslint']
});

resolveOne(toResolve: string, root?: string, options?: IResolveOptions)

resolveMany(toResolve: string[], root?: string, options?: IResolveOptions)

IResolveOptions

cache

  • Type: String
  • Default: .

The root directory of the project to search the module.

resolveDir

  • Type: Boolean
  • Default: false

Return the path to the directory where the module was found.

resolveOnlyByPrefix

  • Type: Boolean
  • Default: false

Skip search modules in the default directories and search them only by npm config get prefix.

Changelog

See the Releases section of our GitHub project for changelogs for each release version.

License

This software is released under the terms of the MIT license.