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

@boiler-dev/boiler

v0.0.1

Published

Local package manager

Readme

boiler

🥘 Local package manager

Why

Boiler is a faster, less formal alternative to remote package managers.

  • Local — Only depends on the local filesystem.
  • Hackable — Modify package files anywhere they're installed.
  • Repairable — Easily copy changes back to the package source.
  • Informal — No versioning except your own optional version control.

Boiler aims to keep code reusable and updatable ("move fast and break things") while removing risks associated with rigid code separation ("version and package everything").

Install

npm install @boiler-dev/boiler

CLI

  • boiler create — Create a package (a named group of file or directory sources).
  • boiler install — Install package files using an identical directory structure as the source.
  • boiler push — Push local package changes back to the source.
  • boiler list — List available and installed packages.

Create package

npx boiler create [package-name] [path...]

⚠️ Paths must be within the current project's root directory.

Install packages

npx boiler install [package-name...]

Push packages

npx boiler push [package-name...]

List packages

npx boiler list

Configuration

CLI commands look for project configuration in the current working directory, and then its parent directories.

If a project configuration is found, that directory is considered the project root path. Otherwise, the current working directory becomes the home to a new project configuration file.

Additionally, the CLI uses a configuration file in the home directory.

Locations

| Directory | Filename | Contents | | :--- | :--- | :--- | | Project (.) | boiler.json | Package file paths (by package name) | | Home (~) | .boiler.json | Project directory paths (by package name) |

Format

{
  "packages": {
    "package-name": {
      // Project
      "installedPaths": [] // Installed package file paths (relative)
      "sourcePaths": []  // Source package file paths (relative)

      // Home
      "projectPaths": [] // Project directory paths (absolute)
    }
  }
}

Register existing projects

Running boiler within any project (even without arguments) will register that project in the home configuration and make its packages available for installation.

Safety

Boiler only modifies a file if it is (1) tracked in git and (2) has no uncommitted changes.

If both conditions are not met, you are prompted to confirm or deny any changes.