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

stamp-pkg

v0.0.1

Published

stamp packaging files such as package.json and readme files to multiple distributions

Readme

stamp-pkg

stamp packaging files such as package.json and README.md files into multiple build directories

Usage

stamp-pkg    // default config file name = stamp-pkg.config.js
stamp-pkg config.file.js    // optional config file name

Configuration

  • package_src: string = source package.json location
  • package_dest: string = destination package.json location
  • package_ignore: string[] = list of attributes to ignore in package.json
  • package_redefine: object[] = list of attributes to redefine in package.json
    • key: string = attribute name in package.json
    • value: string = value for previous attribute in package.json
  • readme_src: string = source README.md location
  • readme_dest: string = destination README.md location
  • readme_ignore: string[] = list of sections to ignore in README.md by header value
  • readme_placeholder_values: object[] = list of placeholders to be filled in README.md
    • key: string = placeholder patterns in README.md
    • value: string = value to fill in the placeholder
    • package: string = package.json value to fill in the placeholder

Example stamp-pkg.config.js:

module.exports = [
  {
    package_src:"package.json",
    package_dest:"packages/stamp-pkg/package.json",
    package_ignore:[
      "scripts","devDependencies"
    ],
    package_redefine:[
      {
        key:"name",
        value: "stamp-pkg-cli"
      }
    ],
    readme_src: "templates/README.md",
    readme_dest: "packages/stamp-pkg/README.md",
    readme_ignore: [
      "Description", "Notes"
    ],
    readme_placeholder_values:[
      {
        key:"{{title}}",
        value: "stamp-pkg-cli"
      },
      {
        key:"{{version}}",
        package: "version"
      },
    ],
  }
]

In package.json

Define stamp-pkg in the postbuild in scripts attribute in package.json. This way once the build creates multiple distribution directories, stamping the package.json and README.md would be done as a postbuild process.

{
  "scripts": {
    "build": "rollup -c",
    "postbuild": "stamp-pkg"
  }
}