jest-cli 30.x

Use jest-cli 30 programmatically and avoid Jest 29 CLI/API shapes.

For

jest-cli@30.5.1

Verified

2026-09-08, 2 examples executed

Package

@modootoday/pmcp-jest-cli@30.0.0

What it covers

• Surface
• Parse CLI arguments with `buildArgv`
• Run Jest programmatically
• Inspect the option definitions
• Jest 30 CLI changes
• Rename `--testPathPattern`
• `--init` was removed
• Filter result shape
• Common Jest 29-era mistakes
• Runtime requirements
• Not covered

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import assert from 'node:assert/strict';
import {buildArgv} from 'jest-cli';

const argv = await buildArgv(['--runInBand']);
assert.equal(argv.runInBand, true);

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-jest-cli

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.