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

install-em

v0.0.4

Published

NodeJS utility for dependency management.

Readme

install-em

NodeJS utility for dependency management.

Example

manifest.json

{
    "production": {
        "react": "^16",
        "react-dom": "^16"
    },
    "build": {
        "webpack": "^5",
    },
    "code-quality": {
        "eslint": "latest"
    }
}

terminal:

install-em -m manifest.json -t /Users/me/example/ build code-quality

CLI

Options

-m, --manifest: path to directory/json-file, where manifest is located (looks for package.json, if directory is given, and looks for ./package.json of current directory, if no parameter given)

-t, --target: installation destination directory (would create node_modules there)

-f, --force: reinstall dependencies, even they are already installed.

Custom groups

You free to use any group names, that satisfy /[a-zA-Z0-9_-]+/.

Group aliases

Also, there is some aliases to use with standard package.json files:

-p, --prod: use dependencies group

-d, --dev: use devDependencies group

-o, --optional: use optionalDependencies group

example:

{
    "dependencies": {
        "lodash": "4"
    },
    "devDependencies": {
        "rimraf": "latest"
    },
    "foo": {
        "left-pad": "^1.3.0"
    }
}
install-em -p --dev -f foo

executes in current directory:

npm install --no-save --force lodash@4 rimraf@latest left-pad@^1.3.0

API

const { installDependency, installDependencies } = require('install-em');

installDependency(name, version, path[, opts])

name (string): dependency name

version (string): dependency version

path (string): installation destination folder

opts (object)

opts.force (boolean): reinstall dependency, even it's already installed in destination directory (false, by default)

returns: Promise

installDependencies(dependencies, path[, opts])

dependencies (Array): array of name/version pairs, like [[name, version], [name, version]]

path (string): installation destination folder

opts (object)

opts.force (boolean): reinstall dependency, even it's already installed in destination directory (false, by default)