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

test-related

v1.1.0

Published

Run tests related to changed source files using AST-based dependency analysis

Readme

test-related

npm version GitHub

Run tests related to changed source files using AST-based dependency analysis (tree shaking).

Why

I wanted to run only the relevant tests for changed files with lint-staged.

Existing tools like Jest's --findRelatedTests don't work with Node.js's built-in node:test runner.

This tool uses TypeScript's AST to build a precise dependency graph, tracking which specific exports from source files are used by tests. When a source file changes, only tests that actually use its exports are triggered.

Installation

npm install -D test-related
yarn add -D test-related
pnpm add -D test-related

Usage

With lint-staged

{
  "lint-staged": {
    "src/**/*.ts": [
      "eslint --fix",
      "typecheck-files",
      "test-related"
    ],
    "test/**/*.ts": [
      "eslint --fix",
      "test-related"
    ]
  }
}

Tip: typecheck-files type-checks only changed files while respecting your tsconfig.json—perfect for fast pre-commit workflows.

CLI

test-related src/index.ts src/utils.ts

Programmatic API

import { findRelatedTests } from "test-related"

const result = findRelatedTests(["src/index.ts", "src/utils.ts"])

console.log(`Running ${result.testFiles.length} related tests...`)

// Run with node:test
const { execSync } = await import("node:child_process")
execSync(`node --test ${result.testFiles.join(" ")}`, { stdio: "inherit" })

How it works

  1. Parse test files - Extracts all imports using TypeScript AST
  2. Parse source files - Extracts all exports (functions, classes, types, interfaces, enums)
  3. Build dependency graph - Maps which tests use which exports
  4. Match changed files - When a source file changes, finds tests that import its exports

Tree-shaking precision

// Source file: src/math.ts
export function add(a: number, b: number): number { return a + b }
export function subtract(a: number, b: number): number { return a - b }

// Test file: test/math.test.ts
import { add } from "../src/math.js"  // Only uses 'add'

test("add works", () => { ... })  // This test runs
// No test for 'subtract' exists

If you change subtract() but not add(), the test won't run—because no test uses subtract.

Options

interface Options {
  /** Working directory (defaults to process.cwd()) */
  cwd?: string
  /** Test directory patterns (defaults to ["test", "src"]) */
  testDirs?: string[]
  /** Source directory patterns (defaults to ["src"]) */
  sourceDirs?: string[]
  /** Always run tests matching this pattern when source files change */
  alwaysRunPatterns?: string[]
  /** Test runner command (defaults to "node --test") */
  testRunner?: string
}

Limitations

  • TypeScript/JavaScript only - Requires .ts or .js files
  • Static analysis only - Runtime dependencies (dynamic imports) are not tracked
  • Export precision - Namespace imports (import * as x) always trigger tests (can't determine specific usage)

For full coverage, run all tests in CI:

node --test

License

MIT