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

lockfile-affected

v2.3.0

Published

CLI for identifying affected monorepo packages from lockfile changes

Readme

lockfile-affected

CI npm version

Warning: This tool is still in early development. The API may change, and some features are incomplete or not yet fully tested. Use in production at your own risk.

Find which workspace packages are affected by lockfile changes.

Purpose

In monorepos, it is hard to build automation that reacts reliably to transitive dependency updates recorded only in lockfiles.

That gap can prevent dependency and security fixes from being rebuilt, retested, and deployed in the workspace packages they actually impact.

lockfile-affected maps lockfile deltas to affected workspace packages so Git and CI pipelines can react deterministically.

Installation

Install globally when you want a persistent lockfile-affected command:

npm install -g lockfile-affected
# or
pnpm add -g lockfile-affected

Install in a repository:

pnpm add -D lockfile-affected

Usage

Pass the before and after lockfile snapshots as arguments. Use shell process substitution to avoid temp files:

# Compare against a specific branch
lockfile-affected <(git show origin/main:pnpm-lock.yaml) pnpm-lock.yaml

# Compare against the merge base (typical CI usage)
BASE=$(git merge-base HEAD origin/main)
lockfile-affected <(git show $BASE:pnpm-lock.yaml) pnpm-lock.yaml

Or pipe the before snapshot via stdin using - (works with npx):

git show origin/main:pnpm-lock.yaml | npx lockfile-affected - pnpm-lock.yaml

Works with pnpm, npm, yarn (classic v1 and berry v2+), and Bun lockfiles (bun.lock). Format is auto-detected from content, or use --format to override.

Options

--workspace <path>         Root directory to search for package.json files (defaults to cwd)
--format <pnpm|npm|yarn|bun> Lockfile format override (auto-detected from content by default)
--json                     Output as a JSON array instead of newline-separated
--deps                     Include production dependencies
--dev                      Include dev dependencies
--peer                     Include peer dependencies
--optional                 Include optional dependencies
                            (when no dep flags are set, all types are included)
--root-deps-affect-all     Treat root dependency changes as affecting all packages
--order <alphabetical|topological> Output order (default: alphabetical)
--help                     Show help

Related packages