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

@goldenbrick/package-build-order

v0.2.5

Published

Determines the dependency order in which to build npm packages.

Downloads

4

Readme

package-build-order

Build Status NPM version

Determines the dependency order in which to build packages.

Usage

  • Use buildOrder to get a single string[] of builds in series.
  • Use getBuildTracker to get a tracker that tracks which packages become available to build when others complete.

buildOrder

buildOrder takes in settings object providing an Object or Map member named paths linking package names to their folder or package.json paths. It returns a Promise for the order in which the packages should be built.

For example, if second has a dependency on first in its package.json, the order would be ["first", "second"].

import { buildOrder } from "package-build-order";

Passing a traditional Object:

const order = await buildOrder({
    paths: {
        first: "./path/to/first",
        second: "./path/to/second"
    }
});

Passing a Map:

const order = await buildOrder({
    paths: new Map([
        ["first", "./path/to/first"],
        ["second", "./path/to/second"]
    ]
}))

getBuildTracker

buildOrder takes in settings object providing an Object or Map member named paths linking package names to their folder or package.json paths. It returns a Promise for a tracker object with two methods:

  • getAvailablePackages - Returns a string[] with all packages that are able to build.
  • markCompleted - Marks a package as completed and returns a string[] of any packages that are now available to build.

If markCompleted returns an empty [], that indicates all possible packages have been completed.

import { getBuildTracker } from "package-build-order";

const tracker = await getBuildTracker({
    paths: {
        first: "./path/to/first", // dependencies: []
        second: "./path/to/second" // dependencies: ["first"]
    }
});

tracker.getAvailablePackages(); // ["first"]
tracker.markCompleted("first"); // ["second"]
tracker.getAvailablePackages(); // ["first", "second"]

Settings

You can also pass direct references to .json files, provided they provide "dependencies" as an array of project names.

const order = await buildOrder({
    paths: {
        first: "./path/to/first/package.json",
        second: "./path/to/second/custom-settings.json"
    }
});

Requires Node >= 7