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

othernpm

v2.0.0

Published

Run npm commands in other directories

Readme

Othernpm

npm version Travis Build Status App Veyor Build status Coverage Status Dependency Status devDependency Status

Othernpm provides a way to run npm commands in other directories. A typical use of this module would be to run npm scripts of subdirectories that have own package.json.

Usage

CLI

Othernpm allows you to specify a path where npm commands run.

# 'cd ./templates && npm install'
% onpm ./templates install

You can also define paths in package.json and use them to specify a path.

{
  "name": "package name",
  ...
  "othernpm": {
    "examples": "./examples",
    "site": "./site"
  }
}
# 'cd ./site && npm run build'
% onpm site run build

# 'cd ./examples && npm test'
% onpm examples test

For example, this repository defines a npm-script named eg in its package.json. By this, we can run any npm command in test/example from the root directory like:

# Check defined npm-scripts in 'test/example'.
% npm run eg -- run

# Install Mocha as a dev-dependency of 'test/example'.
% npm run eg -- install --save-dev mocha

Node.js API

Othernpm also provides API used in Node.js scripts. The module loads configurations from package.json automatically so that you can use them as functions.

const onpm = require('othernpm');

// Run the 'start' script in the examples directory.
onpm.examples('start');

// Run the 'build' script in the site directory.
onpm.site('run build');

// Run npm commands in another directory.
onpm('./templates')('test');

The othernpm function returns a spawn object.

const build = onpm.examples('run build');
build.on('exit', exitCode => console.log(exitCode));

Installation

npm install --save-dev othernpm

License

MIT