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 🙏

© 2025 – Pkg Stats / Ryan Hefner

mako-cli

v2.1.1

Published

A CLI for the mako build runner

Readme

mako-cli

A command line interface for running mako builds.

npm version npm dependencies npm dev dependencies

Install

This can be installed via npm:

sudo npm install -g mako-cli

This will install it globally, but using it locally is likely more flexible. Either way, you get access to a mako command that you can run.

Usage

This tool takes configuration from a file, rather than passing options directly to the CLI. This was chosen because it was more flexible and easier to maintain. You can load config from either a .makorc file, or in your package.json under a property called mako.

{
  "entries": [
    "index.{js,css}"
  ],
  "plugins": [
    "mako-browser"
  ]
}

Upon running mako, it will load the mako-browser plugin and run on the entry files index.js and index.css.

API


  Usage: mako [options] [entries...]

  Options:

    -h, --help           output usage information
    -V, --version        output the version number
    -C, --cache          turn on caching
    -v, --verbose        turn on verbose logging
    -w, --watch          rebuild when changes occur
    -q, --quiet          only log errors

If you specify any entries, it will use those in place of those specified in the mako.json, allowing you to do only a subset of the overall build.

Debugging

Currently, the logging is very minimal. This will be improved in future versions, but in the meantime, you can leverage the underlying debug tool by adding DEBUG=mako* to your command prompt.

$ DEBUG=mako* mako index.js