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

mkstack

v3.0.0

Published

manage npm stacks

Downloads

6

Readme

mkstack

Create and apply your favorite npm stacks.

npm Node version Build Status JavaScript Style Guide

Install

$ npm install mkstack -g

Usage

Create a stack

$ mkstack -c|--create :id

Lets setup a web stack. We need browserify and some other stuff.

$ mkdir ~/new-web-project && cd ~/new-web-project && npm init --yes
$ npm i browserify --save
$ npm i shoe --save --save-exact
$ npm i send --save --save-exact
$ npm i node-sass --save
$ npm i tape --save-dev
$ npm i nodemon --save-dev --save-exact

Save it.

$ mkstack -c web
Created web

Apply stack(s)

$ mkstack -a|--apply :ids [-y|--yarn]

Time for a new web project. Create a new folder and apply the previously saved stack. This will do:

  • npm i :project --save for all dependencies
  • npm i :project --save-dev for all devDependencies.

Use -y or --yarn if you want to use yarn instead of npm

$ mkdir ~/next-project && cd ~/next-project && npm init --yes
$ mkstack -a web
Applying web
..

If you create your stack abstractions well you can combine them. Perhaps you want a test stack that contains your favorite test modules, e.g. tape, chai, phantomjs etc.

Note that the order of the stacks are important since npm will save package.json each time and update in the order the stacks are applied.

$ mkstack -a web
$ mkstack -a sockets
$ mkstack -a tcp-server
$ mkstack -a irc2
$ mkstack -a console

Or use a comma separated list. This is more optimal since the dependency configuration will be merged before doing npm install to avoid installing modules multiple times to save time.

$ mkstack -a web,sockets,tcp-server,irc2,console
Applying web,sockets,tcp-server,irc2,console
..

List stacks

$ mkstack -l|--list

List your saved stacks with the -l flag. Note that mkstack does not have any opinions on version numbers. It just saves them as you specified them the first time.

$ mkstack -l
{
  "web": {
    "dependencies": {
      "browserify": "^8.1.1",
      "node-sass": "^2.0.0-beta",
      "send": "0.11.1",
      "shoe": "0.0.15"
    },
    "devDependencies": {
      "nodemon": "1.3.2",
      "tape": "^3.4.0"
    }
  }
}

Remove stack

$ mkstack --rm :id

$ mkstack --rm web
Removed web
$ mkstack -l
No stacks found

Config

mkstack uses rc. Default path for current config file is ~/.mkstackrc but that can be changed by using the --config flag:

$ mkstack -c websockets --config ~/path/to/my/stacks

License

GPL-3.0 © 2018-present Lars-Magnus Skog.