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

module-search

v0.2.4

Published

A simple utility library for locating the directory of a module

Downloads

1

Readme

Module Search

Module Search is a simple utility library to assist in locating a module.

Installation

Install simply by using:

npm install module-search --save-dev

or

yarn add module-search --dev

Usage

The following functions are exported:

getModulePath(packageName, options)

This function returns the directory of a module. If no match is found null will be returned.

Parameters:

  • The packageName argument should be used to define the package you want to locate.
  • The options argument is optional. It can provide further specification about where to search. It should be an object and can contain the following properties:
    • cwd - defines the current working directory. The default value is the directory the process is running in.
    • directories - a string array defining all the followings that can contain modules. The default value is ['node_modules', 'web_modules'].

getPackageJson(packageName, options)

This function return the package.json file of a module. If no match is found null will be returned.

Parameters:

  • The packageName argument should be used to define the package you want to locate.
  • The options argument is optional. It can provide further specification about where to search. It should be an object and can contain the following properties:
    • cwd - defines the current working directory. The default value is the directory the process is running in.
    • directories - a string array defining all the followings that can contain modules. The default value is ['node_modules', 'web_modules'].

getPackageMain(packageName, options)

This function return the main file path of a module. If no match is found null will be returned.

Parameters:

  • The packageName argument should be used to define the package you want to locate.
  • The options argument is optional. It can provide further specification about where to search. It should be an object and can contain the following properties:
    • cwd - defines the current working directory. The default value is the directory the process is running in.
    • directories - a string array defining all the followings that can contain modules. The default value is ['node_modules', 'web_modules'].