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

prebuild-ci

v4.0.0

Published

Use CI to auto upload prebuilds

Readme

prebuild-ci

Use CI like GitHub Actions, Travis and AppVeyor to auto upload prebuilds. Requires you to use prebuild@6 or later.

npm Node version Test Standard

Motivation

It's great to provide prebuilds with your native node modules, so consumers don't have to compile them on install - a pre made binary will simply be fetched. It can however be cumbersome to create those binaries yourself, you need to run the appropriate scripts on every OS you desire to ship. This module provides an alternative by creating and uploading those binaries in the CI environments you use, so for example using travis and appveyor you can cover all node versions on mac OS, linux and windows, automatically!

Usage

Add prebuild-ci to your "test" script or CI configuration, like this:

  "scripts": {
    "test": "mocha && prebuild-ci"  
  }

Also configure your CI environments to set the environment variable PREBUILD_TOKEN to your prebuild upload token, and make sure this variable is only set on pull requests from the same repository.

Then, whenever a CI job passes and updates "version" in the module's package.json, the prebuild for the current environment will be uploaded to GitHub.

That means that in order to have prebuilds for all desired os / node combinations, make sure to run each of those in a CI job.

Pro Tip: In order for prebuilds to be available as soon as a new version is published to npm, wait with the actual npm publish until all the CI jobs have completed.

Installation

$ npm install --save prebuild-ci

License

MIT