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

package-change-checker

v1.2.4

Published

Run npm install when package json dependency changes

Downloads

25

Readme

Package Change Checker

Run an npm install (or anything else you want!) when package json dependencies change between ORIG_HEAD and HEAD. Suggested use as a githook, on post-merge for example.

Usage

Add package-change-checker to your dev dependencies and call it as part of a githook, or an npm command, or just globally install and use it manually.

Supported Arguments

  • Can override the ORIG_HEAD and HEAD defaults by passing commits/tags/branches, first commit will override ORIG_HEAD, second overrides HEAD. e.g. package-change-checker 39ddb32 1d62193
  • --install-cmd="...":
    • Default: npm install
    • If the default npm install command is not suitable, you can override it, e.g.;
      • --install-cmd="npm install && npm run bootstrap"
      • --install-cmd="echo 'Warning! Dependencies have changed!
  • --quiet:
    • Default: false
    • By default package-change-checker will log out if there are changes or not, and will log out the command to run. If you're just echoing out a warning on change, you probably want to include this argument.

Env Flags

If you wish to disable the checker completely you can add PACKAGE_CHANGE_CHECKER_DISABLED=true to your env. This will skip all behaviour and logging.