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

@autotests/playwright-impact

v0.1.5

Published

Core impacted-test selection library for changed POM/method analysis

Downloads

607

Readme

Playwright Spec Impact

If you use Playwright + POM and your CI runs are slow, this library selects only specs affected by your changes.

It reads changed files, finds impacted specs, and helps you run only what matters.

Install

// npm
npm i @autotests/playwright-impact

// pnpm
pnpm add @autotests/playwright-impact

Quick Start (Copy & Run)

Minimal working code

Create impact.js in your repo root:

const { analyzeImpactedSpecs } = require('@autotests/playwright-impact');

const result = analyzeImpactedSpecs({
  repoRoot: process.cwd(),
  profile: {
    testsRootRelative: 'tests',
    changedSpecPrefix: 'tests/',
    isRelevantPomPath: (filePath) =>
      (filePath.startsWith('src/pages/') || filePath.startsWith('src/utils/')) &&
      (filePath.endsWith('.ts') || filePath.endsWith('.tsx')),
  },
});

if (!result.hasAnythingToRun) {
  console.log('No impacted specs found');
  process.exit(0);
}

for (const spec of result.selectedSpecsRelative) {
  console.log(spec);
}

Save as impact.js

Run: node impact.js

Use output paths in your Playwright CLI

What you need to change

You only need to adjust:

  • testsRootRelative: folder where your Playwright specs live.
  • changedSpecPrefix: prefix used to detect directly changed specs.
  • isRelevantPomPath: rule for which source files are treated as POM/utility inputs.

Example output

Example output:

tests/auth/login.spec.ts
tests/cart/cart.spec.ts

If nothing is impacted:

No impacted specs found

Minimal CI Script

Use this when your branch is compared to origin/main.

const { analyzeImpactedSpecs } = require('@autotests/playwright-impact');

const result = analyzeImpactedSpecs({
  repoRoot: process.cwd(),
  baseRef: 'origin/main',
  profile: {
    testsRootRelative: 'tests',
    changedSpecPrefix: 'tests/',
    isRelevantPomPath: (filePath) =>
      (filePath.startsWith('src/pages/') || filePath.startsWith('src/utils/')) &&
      (filePath.endsWith('.ts') || filePath.endsWith('.tsx')),
  },
});

if (!result.hasAnythingToRun) {
  console.log('No impacted specs found');
  process.exit(0);
}

console.log(result.selectedSpecsRelative.join(' '));

Typical CI Usage

  1. Compare current branch with origin/main.
  2. Compute impacted specs.
  3. Exit with 0 if nothing should run.
  4. Pass selectedSpecsRelative to your Playwright runner.

How It Works (High Level)

  1. Read changed files from Git.
  2. Include directly changed specs.
  3. Detect impacted specs from changed POM/utility code.
  4. Return a final spec list.

Advanced Config

Required:

  • repoRoot
  • profile.testsRootRelative
  • profile.changedSpecPrefix
  • profile.isRelevantPomPath(filePath)

Optional:

  • analysisRootsRelative
  • fixturesTypesRelative
  • baseRef
  • includeUntrackedSpecs
  • includeWorkingTreeWithBase
  • fileExtensions
  • selectionBias

Advanced Diagnostics

  • warnings
  • selectionReasons
  • coverageStats.uncertainCallSites
  • coverageStats.statusFallbackHits
  • changedEntriesBySource

Reason Codes

  • direct-changed-spec
  • matched-precise
  • matched-uncertain-fail-open
  • retained-no-bindings