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

node-build-number

v1.0.2

Published

A node extension for capturing build number, timestamp and other metadata into the npm package.json

Readme

NBN

This package (abbreviated as "NBN") updates the package.json of your project with build information. You only need to add the nbn cli command to your build steps to have the build info updated, and the build number incremented.

"scripts": {
    "build": "nbn && npm run project-dist-task"
}

Unique ID

NBN also generates a unique build ID example: node-build-number:v1.0.0-master[build:4] from the project name, version, build number and current branch (only supports git at this time). This ID can be useful when you need to identify builds, it will be in the package.json of your project code. Displaying it in the header or footer of a web application in dev or testing will tell you whether a build you deployed is successfully running, or if something is wrong.

Example of build metadata in package.json

"build": {
    "unique": "node-build-number:v1.0.0-master[build:4]",
    "number": 4,
    "timestamp": "6/16/2020, 8:24:38 PM",
    "git-branch": "master",
    "git-version": "2.26.2",
    "node-version": "v14.2.0",
    "computer": "SCRAPTOP",
    "os": "Windows_NT",
    "arch": "AMD64",
    "user": "MrExampleton"
  }
  

Incrementing the Version Number

Supposing you have a project with version 0.3.6 and build 12. The following commands will bump the version up as shown in the examples below.

nbn --major

Version 1.0.0 build 0.

nbn --minor

Version 0.4.0 build 0.

nbn --rev

Version 0.3.7 build 0.