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 🙏

© 2024 – Pkg Stats / Ryan Hefner

before-every-install

v1.0.0

Published

resolve npm dependencies and examine package metadata _before_ zero-day scripts are downloaded onto your machine

Downloads

1

Readme

before-every-install

resolve npm dependencies and examine package metadata before zero-day scripts are downloaded onto your machine

$ npm install before-every-install
var beforeEveryInstall = require('before-every-install')

beforeEveryInstall(function logPackageVersion(pkg) {
  console.log(pkg.version)

  // pkg is an object containing package metadata returned by the registry
  // eg: for this package v1.0.0
  // http://registry.npmjs.org/before-every-install/1.0.0
})

why

Sometimes it's useful to know exactly what packages and tarballs npm is going to witchcraft onto your machine.

Now you can do that before the files are downloaded and extracted.

how

By abusing the internal npm install API and enabling the dry-run flag, we can resolve all dependencies and retrieve package metadata without actually downloading the package contents.

Since the npm CLI isn't intended to be used programmatically we lock into an exact version (currently, 3.8.3) to ensure the private API we are taking advantage of doesn't mysteriously change. We also use a worker process when invoking the install command because I burned an hour trying to figure out how to silence logging without success.

Mo processes less problems

note

Remember, there isn't any guarantee that the packages resolved by this module are the ones you'll get on a subsequent npm install. This is a serial operation and things could change in between operations.