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

run-on-changed

v0.4.0

Published

Runs a command on the files you changed plus every JS/TS file that transitively imports them. 🎯

Downloads

6,323

Readme

Usage

Run a command on every file impacted by your changes: the files you changed, plus every JS/TS file that transitively imports them. The import/export graph is parsed in-memory with the native oxc parser and resolver, so a file is included whenever it (transitively) imports something you changed — exactly what typed linting needs.

CLI

Pass the command to run after --; impacted file paths are appended as arguments:

npx run-on-changed -- npx eslint --fix

By default it uses your working-tree changes. Diff against a base ref instead with --since, and override which files form the graph with one or more --files globs:

npx run-on-changed --since origin/main -- npx eslint
npx run-on-changed --files "src/**/*.ts" -- npx prettier --write

TypeScript path aliases (compilerOptions.paths) are resolved from a tsconfig.json in the current directory, so aliased imports are followed just like relative ones. Point at a different config with --tsconfig:

npx run-on-changed --tsconfig configs/tsconfig.json -- npx eslint

Node.js API

import { runOnChanged } from "run-on-changed";

const exitCode = await runOnChanged({
	command: ["npx", "eslint", "--fix"],
	cwd: process.cwd(),
	since: "origin/main", // optional
	files: ["src/**/*.ts"], // optional
	tsconfig: "configs/tsconfig.json", // optional
});

Debugging

run-on-changed logs what it decides through debug-for-file. Set the DEBUG environment variable to see the changed files, the project-file count, and the full list of impacted files handed to your command:

DEBUG=run-on-changed:* npx run-on-changed --since origin/main -- eslint

runOnChanged returns the spawned command's exit code, or 0 when nothing is impacted. Lower-level building blocks (buildDependencyGraph, reverseGraph, collectImpactedFiles, parseFileSpecifiers, createResolveSpecifier, getChangedFiles, enumerateProjectFiles) are exported too.

Development

See .github/CONTRIBUTING.md, then .github/DEVELOPMENT.md. Thanks! 🎯

Contributors

💝 This package was templated with create-typescript-app using the Bingo framework.