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

@systemfsoftware/stryker-js-typescript-checker

v8.2.1

Published

TypeScript checker plugin for Stryker — TS7 native

Readme

@systemfsoftware/stryker-js-typescript-checker

License: Apache-2.0 npm version

TypeScript checker plugin for Stryker mutation testing — provides native support for TypeScript 5.x through 7.x.

Why Use a Type Checker Plugin?

Mutation testing modifies code syntax in ways that may cause compiler errors (e.g. invalid type assignments, breaking return type contracts). Without a checker plugin, those mutants execute in your test runner, waste runner execution time, or trigger misleading test runner errors.

The TypeScript checker intercepts mutants before they reach the test runner. If a mutant causes a TypeScript compilation failure, it is classified immediately as CompileError without spinning up test runner workers.

Prerequisites

  • Node.js >=22.18.0
  • TypeScript >=5.0.0
  • @systemfsoftware/stryker-js >=5.0.0

Install

pnpm add -D @systemfsoftware/stryker-js-typescript-checker typescript

Setup in stryker.config.ts

import { defineConfig } from '@systemfsoftware/stryker-js/config'

export default defineConfig({
  checkers: ['typescript'],
  plugins: ['@systemfsoftware/stryker-js-typescript-checker'],
  // Optional custom tsconfig path (defaults to tsconfig.json)
  // tsConfigFile: 'tsconfig.build.json',
})

In-process runtime (./runtime)

The default entry is the worker plugin Stryker loads from plugins, and that is all a normal setup needs. Tooling that drives the compiler itself — for example an oracle that instruments a project and hands the mutants to the real checker — can import the in-process runtime from the ./runtime subpath instead:

import { CheckerRuntime, nodes, TypeScriptCompiler } from '@systemfsoftware/stryker-js-typescript-checker/runtime'

It publishes the runtime Layer (CheckerRuntime.layer(options)), its CheckerRuntimeShape type, the TypeScriptCompiler service tag and the nodes program-graph accessor. Everything else stays behind the worker entry.

License

Apache-2.0