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

greenjam

v1.0.1

Published

Logs a message to the console when the package is installed.

Readme

install-logger

A tiny demo package that prints a message to the console when it's installed, using npm's postinstall lifecycle hook.

How it works

package.json defines several install-time lifecycle hooks:

"scripts": {
  "preinstall": "node lifecycle.js",
  "install": "node lifecycle.js",
  "postinstall": "node lifecycle.js",
  "prepare": "node lifecycle.js"
}

When the package is installed as a dependency, npm runs these hooks in order (preinstallinstallpostinstall, plus prepare for git/local/link installs). lifecycle.js reads npm_lifecycle_event and console.logs which hook fired.

Why postinstall might not run

Not every package manager runs dependency lifecycle scripts. Bun and pnpm block them by default for security and only run them for packages you explicitly trust:

  • Bun: add the package to trustedDependencies in the installing project's package.json, then reinstall. Without it, none of these hooks run.
  • pnpm (v10+): approve with pnpm approve-builds, or list the package under pnpm.onlyBuiltDependencies.
  • npm: runs them by default unless --ignore-scripts is set.

Try it locally (without publishing)

# from another folder
npm install /path/to/install-logger

You'll see the install message printed.

Publishing

  1. Change name in package.json to something unique (or keep the @yourusername scope and swap in your npm username).
  2. npm login
  3. npm publish --access public