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

@olegjs/on-change

v3.0.1

Published

CLI tool to run a command if file has changed since the last time that command was run

Downloads

309

Readme

on-change

npm install size Node.js CI Coverage Status GitHub last commit

CLI tool to run a command if file has changed since the last time that command was run.

Forgetting to run npm i or npm ci every time after git pull or switching between branches and getting Error: Cannot find module...? Add the following to package.json to automate this chore.

"scripts": {
  "prestart": "npx @olegjs/on-change --file package-lock.json npm ci"
}

This CLI tool stores a file checksum in a hidden sha file every time it run a given command. Made to automate running npm ci after pulling modified package-lock.json.

Install

npm install --save-dev @olegjs/on-change

Usage

npx @olegjs/on-change --help

# Usage: on-change --file [file] [command]
#
# Options:
#   --help      Show help                                                [boolean]
#   --version   Show version number                                      [boolean]
#   --file, -f  Path to file to check for changes              [string] [required]
#   --color     Force color or disable with --no-color                   [boolean]
#
# Examples:
#   on-change --file package-lock.json npm    Reinstall dependencies on changed
#   ci                                        package-lock.json