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

hello-postinstall

v0.0.5

Published

Example npm package with greet() and a postinstall hook demo

Readme

hello-postinstall

Small package with greet() and a postinstall hook that sends a POST to the telemetry endpoint (same contract as apps/hello-postinstall: empty body, expect 204).

What postinstall does

On install, the script POSTs to:

  • https://hello-postinstall.vercel.app/api/telemetry by default (the demo deployment for this repo), or
  • whatever URL you set in HELLO_POSTINSTALL_URL, or
  • whatever URL you set as hello_postinstall_url in an .npmrc (project, user, or global). npm exposes .npmrc keys as npm_config_<key> env vars during lifecycle scripts, which is how the hook reads it.

Set HELLO_POSTINSTALL_URL (or hello_postinstall_url in .npmrc) to an empty string to skip the request entirely. The env var takes precedence over .npmrc.

Optional HELLO_POSTINSTALL_UPLOAD_FILE: path to a local text file; its UTF-8 contents are sent as the POST body (Content-Type: text/plain; charset=utf-8). If the path is missing or unreadable, the hook logs a warning and sends an empty body like the default behavior.

If fetch is not available (very old Node), the hook does nothing.

Run the postinstall script

The hook is defined under scripts.postinstall in package.json. Installing dependencies runs postinstall automatically:

npm install

You can also run only the hook (no install):

npm run postinstall

To point at a local or forked server:

HELLO_POSTINSTALL_URL=http://localhost:3000/api/telemetry npm install

…or persist it for a project by adding an .npmrc:

hello_postinstall_url=http://localhost:3000/api/telemetry

To send a local file as the POST body:

HELLO_POSTINSTALL_UPLOAD_FILE=./payload.txt npm install

To disable the network call:

HELLO_POSTINSTALL_URL= npm install

…or in .npmrc:

hello_postinstall_url=