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

mako

v1.1.7

Published

A pluggable general-purpose build tool

Downloads

1,265

Readme

mako (aka: core)

The coordinator for mako builds.

npm version npm dependencies npm dev dependencies

API

mako([options])

Returns a new Runner instance, no need for the new keyword.

Available options:

  • root the project root (default: pwd)
  • plugins a list of plugins to add during init
  • tree a predefined tree (eg: loading from mako-cache)
  • concurrency used internally to set parallel concurrency limits

mako.Runner

The Runner class is exposed publicly to allow for advanced extensions.

runner.use(...plugins) (chainable)

Adds a new plugin to the runner. Each plugin is a Function, so any nested arrays will be flattened, allowing you to nest freely. (particularly useful for bundles)

runner.build(...entries)

The primary public interface, which runs both parse and compile for the given entries. It returns a Promise that resolves with a Build object that contains some information about the build itself.

runner.parse(...entries)

Runs parse for the passed entries. This method isn't typically used directly, but it can be useful for priming the tree for doing watches or inspecting the dependency tree.

It returns a Promise that resolves with a Build object.

runner.compile(...entries)

Runs compile for the given entries, this will skip the parse phase in case you know it has already been finished. (such as when calling runner.parse() manually)

It returns a Promise that resolves with a Build object.

runner.{hook}(extensions, handler)

Registers a handler for a specific hook, see the wiki for more information. There is a different method for each of the available hooks.

Build

This object is returned from each call to build/parse/compile, and it is shared by plugins throughout the build for holding the current tree, tracking timing and interacting with the core runner.

Described below is the public API primarily for end-users, but it is not exposed publicly at this time. Plugin authors should refer to the wiki for more information about plugin-specific APIs.

build.entries

This is an array of the entry files that were triggered for this build.

build.tree

This is a reference to the tree in use during the current phase.

If returned from runner.parse(), it will be a reference to runner.tree, so don't modify this tree unless you know exactly what you're doing.

If returned from either runner.compile() or runner.build(), this will be the same tree used during the compile phase. This tree is safe to modify, but it won't do anything, since the build is already complete.

build.runner

A reference to the runner that initiated this build.