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

jest-impact

v0.0.3

Published

Lists the Jest test files in each Nx project that a commit range can affect, using sovra for the import graph.

Readme

jest-impact (PoC)

Lists the Jest test files in each Nx project that the changes between two commits can affect, so CI can run only those. sovra walks the import graph; this package prepares its inputs and decides when to widen the run.

jest-impact is an independent project for use with Jest. It is not affiliated with or endorsed by the Jest project or the OpenJS Foundation.

Anything the analyzer cannot reason about runs. A false negative (a skipped test that should have run) is the one failure it is designed to avoid.

Usage

npm install --save-dev jest-impact

Needs Node 22.18 or later. sovra ships prebuilt binaries for Linux (x64 and arm64, glibc and musl), macOS on Apple silicon and Windows (x64 and arm64); Intel Macs are not covered.

Run it in a checkout of the head commit, with git history back to the base.

npx jest-impact --base origin/main --head HEAD            # summary
npx jest-impact --base "$NX_BASE" --head "$NX_HEAD" --format nx   # one command per project
npx jest-impact --json report.json --out-dir test-lists   # full report and per-project lists

--format nx prints, for each project that needs to run:

npx nx run shared-product-state:test --runTestsByPath /repo/libs/shared/product/state/src/lib/+state/products.reducer.spec.ts
npx nx run cart:test        # the whole target, when the run had to widen

--runTestsByPath is required: Jest treats plain paths as regexes, and paths such as +state/ silently match nothing.

--format gitlab prints a child pipeline with one job per project that needs to run (or a single no-op job when none does), for GitLab's dynamic child pipelines:

plan-tests:
  stage: plan
  variables:
    GIT_DEPTH: 0
  script:
    - npx jest-impact --base "$CI_MERGE_REQUEST_DIFF_BASE_SHA" --head "$CI_COMMIT_SHA" --format gitlab --gitlab-include ci/jest-job.yml --gitlab-extends .jest > tests.yml
  artifacts:
    paths: [tests.yml]

run-tests:
  stage: test
  needs: [plan-tests]
  trigger:
    include:
      - artifact: tests.yml
        job: plan-tests
    strategy: depend

--gitlab-include adds include: local entries to the child pipeline, and --gitlab-extends makes every job extend a hidden job from them, for image, cache and tags.

The Node API is analyze({ workspaceRoot, base, head }), which returns the same report as --json.

What happens in one run

  1. Config loader. Finds Nx projects (project.json, workspace package.json, or --nx-graph output) and each project's jest.config.*. Configs are evaluated in-process: local files are transpiled with sucrase, installed packages are required for real, and missing ones are stubbed. Nx's own Jest preset has a built-in stand-in, so Nx repos load without an install. Test files are picked like Jest does (roots, testMatch/testRegex, ignore patterns, extensions).
  2. Workspace linker. Symlinks every workspace package into the root node_modules (existing entries are left alone), so sovra resolves imports between packages.
  3. Resolver options. One option set for the workspace: tsconfig.base.json, its customConditions, Jest's customExportConditions, .js to .ts extension aliases, built-in modules, and prefix-shaped moduleNameMapper entries as aliases.
  4. Change collector. git diff base head, plus a base/head lockfile diff (npm 7+, yarn 1, yarn 2+, pnpm 6+). Every changed package, and every direct dependency with a changed package anywhere below it, becomes an npm: entry. Dependency-only edits to package.json files count the same way.
  5. Safety net and sovra. Changed files are classified (below). Code changes, npm: entries and widened projects go to one getAffected call over all test files plus each project's setup files and other runtime inputs. sovra's errors are triaged; files with imports it cannot follow are added as changes in a second call, so every test reaching them runs.
  6. Output. Tests grouped by Nx project and target, with the reason for every widening.

When the run widens

| Situation | Result | | --- | --- | | nx.json, root tsconfig, root Jest config or preset, babel/swc config, pnpm-workspace.yaml, nx.json sharedGlobals files | Run everything | | Root package.json changed beyond dependency ranges and metadata | Run everything | | Lockfile changed and cannot be parsed | Run everything | | A test-tooling package changed (jest, ts-jest, @nx/jest, typescript, ...) | Run everything | | A project's Jest config, preset, config helper, tsconfig*.json, project.json or .babelrc changed | Run that project | | A setup file, transform, environment or other runtime input imports a change | Run that project | | A package the Jest config loads changed (transform, environment, preset) | Run that project | | The config needs a package that is not installed, or uses a custom resolver not in safeResolvers | Run that project, on every run | | A __mocks__ file changed | Run that project | | A non-code file changed inside a project (template, JSON, fixture) | Run that project, and treat its code as changed for importers elsewhere | | A workspace package.json changed beyond dependencies | Same as a non-code file | | Any package.json changed | Code that imports it runs (require('../package.json').version) | | A Jest config that no Nx project contains | Reported as its own project, run with jest --config | | A snapshot changed | Run the test it belongs to | | sovra reports a non-literal require, an unresolved local or workspace import, or a non-prefix moduleNameMapper match; or a file has an import() with a non-literal argument | Every test that reaches that file runs, on every run | | Unresolved third-party import (not installed) | Ignored: matched by name through npm: entries | | jest.mock('./x', factory) | Ignored: the factory replaces the module | | Docs, lint config, CI config (ignoredFiles) | Ignored |

Settings

Optional jest-impact.config.json at the workspace root. Each list given replaces the default.

{
  "safeResolvers": ["@nx/jest/plugins/resolver", "scripts/patched-jest-resolver.js"],
  "conditionNames": ["@nx/nx-source"],
  "trustedFiles": ["packages/nx/src/utils/handle-import.ts"],
  "globalFiles": ["nx.json", "tsconfig.base.json"],
  "ignoredFiles": ["**/*.md"],
  "runnerPackages": ["jest", "jest-*", "@jest/*", "ts-jest"]
}

conditionNames is for repos whose custom resolver adds export conditions that tsconfig does not declare. trustedFiles lists files whose dynamic imports a maintainer has checked; without it, every test reaching them always runs.

Validation so far

  • nx-examples, test lists: identical to jest --listTests for all 9 Jest projects, with and without node_modules installed.
  • nx-examples, impact: each of the 15 test files was run alone under a file-read tracer to record what Jest actually loads. For 172 single-file changes, no test that loaded the changed file was missed. With codegen output present, 96 changes matched the runtime set exactly; the rest over-selected (type-only imports that ts-jest elides, and project-wide widenings for config files). Without codegen output, the unresolved ./generated import in shared-product-types widens every run to the 10 tests that reach it, which is the safety net working as intended.
  • Replays: 60 nx-examples commits and 40 nrwl/nx commits. Almost all of them run everything, correctly: they are Nx/Jest upgrades, or (in nrwl/nx) the remaining Jest suites are e2e tests whose global setup imports the Nx packages themselves. nrwl/nx also shows the cost of dynamic requires in tooling code. Analysis took 0.3 to 0.6 s per commit, or about 5 s when the pnpm lockfile changed.
  • bitwarden/clients fixture (fixtures/bitwarden): 1,481 test files traced in one full Jest run, and 55 cases (37 real commits by category, 18 synthetic patches). All 55 pass with no missed test. Outside the 8 that correctly run everything, the analyzer selects 27.5% of tests on average where 16.4% loaded a changed file; 31 tests reach files sovra cannot follow and run on every change. About 0.9 s per case.
  • Nx output: nx run <project>:test --runTestsByPath <file> ran exactly the listed suite through the inferred @nx/jest/plugin target.

Known gaps

  • File-level only: a barrel re-export means every importer of the barrel is affected.
  • No explain path per test yet; reasons are reported per project and per widening.
  • Lockfile parsing is not cached and dominates run time when the lockfile changes.
  • No moduleNameMapper hook in sovra, so regex mappings fall back to widening.
  • Not yet run on the private pilot repo.

Development

npm install
npm test          # node:test, runs the TypeScript sources directly (Node 22.18+)
npm run typecheck
npm run build     # emits dist/ for the bin

Publishing

Releases publish from GitHub Actions (.github/workflows/release.yml) when a v* tag is pushed:

npm version patch         # or minor / major: bumps package.json, commits and tags
git push --follow-tags    # the Release workflow tests, builds, publishes and creates a GitHub release

The workflow uses npm trusted publishing, so no npm token is stored in the repo. It is set up once on npmjs.com under the package's Settings > Trusted publishing: GitHub Actions, owner pmarchini, repository jest-impact, workflow release.yml, environment npm. npm only offers this for a package that already exists, so the first version is published by hand with npm publish.

npm pack writes the tarball without publishing, to try it locally with npm install ./jest-impact-<version>.tgz.