[CSR-0] chore: Bump @jest/reporters from 30.4.1 to 30.5.0

[dependabot]

Bumps @jest/reporters from 30.4.1 to 30.5.0.

Release notes

Sourced from @​jest/reporters's releases.

v30.5.0

On a personal note: King Harald V of Norway passed away this morning. He ascended the throne 35 years ago, two months before I was born. This release is dedicated to his memory. Hvil i fred 🇳🇴

---

This is a big release. It touches jest-runtime, jest-resolve and jest-haste-map in many places, and with this many changes there might be regressions 😬. If your suite behaves differently after upgrading, please open an issue.

Highlights

whenCalledWith

Mock functions can now configure return values per argument list, contributed by @​timkindberg (#16053):

const fn = jest.fn();
fn.whenCalledWith('apple').mockReturnValue('red');
fn.whenCalledWith('banana').mockReturnValue('yellow');
fn.whenCalledWith(expect.any(Number)).mockReturnValue('numeric');
fn('apple'); // 'red'
fn('banana'); // 'yellow'
fn(42); // 'numeric'
fn('grape'); // undefined

The returned object is a real Mock, so mockReturnValueOnce, mockResolvedValue, mockImplementation etc. all chain here too. Argument slots accept literals or any asymmetric matcher, with the same equality semantics as toHaveBeenCalledWith(). Calls that match nothing fall through to the base mock. See the Mock Functions docs for matching and precedence details.

Describe-level retries

jest.retryTimes() can now retry a whole describe block instead of a single test, contributed by @​soltonigiri (#16322). Each attempt reruns the block's beforeAll/afterAll hooks, child tests and nested describes, which helps when tests in a block depend on shared state:

describe('workflow', () => {
  jest.retryTimes(3, {entireDescribe: true});
test('first step', () => {});
test('second step', () => {}); // a failure retries the entire block
});

New file watcher

The non-watchman path of jest-haste-map is rewritten. @parcel/watcher replaces the homegrown NodeWatcher and FSEventsWatcher (#16188), and fdir replaces the hand-rolled directory recursion in the crawler (#16187). A batch of fixes also makes watching and indexing survive locked files on Windows, watchman failures, and duplicate manual mocks (#16295, #16358, #16355, #16360).

If you can, please run your suite with --no-watchman (in and out of watch mode) to exercise the new crawler and watchers, and report anything odd 👍

Long-requested dependency updates

• babel-plugin-istanbul is updated to v8 (#16049)
• glob is updated to v13 (#16397)

... (truncated)

Changelog

Sourced from @​jest/reporters's changelog.

30.5.0

Features

• [@jest/expect-utils, jest-mock] Add mockFn.whenCalledWith(...args) for configuring return values per argument list, with first-class asymmetric-matcher support (#16053)
• [@jest/expect-utils] Export AsymmetricMatcher and FunctionParameters types (previously private to expect) (#16053)
• [jest-circus, jest-core, jest-jasmine2, jest-test-result, jest-types] --collectTests now expands test.each/describe.each cases and reports per-status counts (skipped/todo via the new wouldRun flag for selected tests) plus a summary line that match a real run, including under --testNamePattern and .only/fdescribe focus on both the circus and jasmine2 runners (#16259)
• [jest-circus, jest-environment, jest-runtime, jest-types] Add describe-level retries via jest.retryTimes(..., {entireDescribe: true}) (#16322)
• [jest-circus, jest-message-util, jest-reporters, jest-types] Add retryMessages to AssertionResult and export formatErrorStack, so the retry log renders nested cause and AggregateError sections with code frames instead of serialized [cause]:/[errors]: markers (#16316)
• [jest-circus, jest-types] Add unhandledErrorsDetailed to Circus.RunResult, so an unhandled rejection reports its cause chain and AggregateError entries with code frames instead of a pre-serialized stack (#16316)
• [jest-haste-map] Replace NodeWatcher and FSEventsWatcher with @parcel/watcher for the non-watchman watch path (#16188)
• [jest-resolve] Bump unrs-resolver to 1.12.1, remove jest-pnp-resolver and unnecessary checks (#15721)
• [jest-resolve] Honor Node's --preserve-symlinks / NODE_PRESERVE_SYMLINKS in the default resolver by passing symlinks: false to unrs-resolver (#16260)
• [jest-runtime] Apply automocking and manual __mocks__ files to synchronously evaluable ESM graphs on Node 24.9+ - static imports, dynamic import() and require() of an ESM file now generate an automock from the real module's namespace instead of failing with "Attempting to import a mock without a factory". Graphs that need async evaluation (top-level await) or an async-only resolver or transformer still throw (#16391)
• [jest-runtime] Route process.getBuiltinModule through the sandbox, so it returns the sandbox process and the hooked node:module instead of the host's (#16391)
• [jest-runtime] Throw an actionable error from module.register() and module.registerHooks() inside a test - the hooks attached to the loader running Jest itself, never saw the sandboxed requires they were meant for, and stayed registered for every later test file in the worker (#16391)
• [jest-runtime] Surface resolution and import-attribute errors in an ESM graph before executing any of its CJS dependencies on Node 24.9+, matching Node's run-nothing-on-a-broken-graph behavior; the legacy loader on older versions keeps its linking-time execution order (#16391)
• [jest-runtime] Throw ERR_SOURCE_PHASE_NOT_DEFINED with an actionable message for import source and import.source(), instead of failing at instantiation with V8's bare "Source phase import object is not defined" (#16391)
• [jest-runtime] Emit the JSON-without-import-attribute deprecation warning once per test file instead of once per worker, so it is no longer silently swallowed for every file after the first (#16391)
• [jest-runtime] Set import.meta.main to true in the test file and false in every module it loads, matching Node 24+ (#16367)
• [jest-runtime] Resolve the module-sync export condition, so a package that exposes its ESM entry point for require() loads the same file Node would (#16336)
• [jest-snapshot] Add external snapshot paths to custom reporter failure details (#16374)

Fixes

• [jest-console, jest-reporters] CustomConsole now buffers console output so TestResult.console is populated for reporters when verbose is enabled, while GitHubActionsReporter avoids replaying buffered output in verbose mode (#16155)
• [expect, jest-message-util, jest-pattern, jest-regex-util, jest-util] Revert node: protocol imports to restore webpack/browser-bundle compatibility (#16167)
• [expect] Widen toMatchObject and objectContaining parameter type from Record<string, unknown> to object so class instances are accepted (#16196)
• [jest-circus] Call a generator test body with the shared test context, so this matches what a regular test function receives (#16347)
• [jest-circus] Capture the error listeners of the parent process instead of the in-sandbox process, so listeners registered before the test file survive teardown and sandbox listeners no longer leak onto the parent (#16347)
• [jest-circus] Clear currentlyRunningTest after skipped and todo tests (#16342)
• [jest-circus] Prevent late done() callbacks from affecting later test or hook invocations (#16343)
• [jest-circus, jest-jasmine2] Honor --expand when formatting node:assert failures, instead of always collapsing the diff (#16347)
• [jest-circus, jest-jasmine2, jest-message-util] Serialize the inner errors of an AggregateError into failureMessages, retryReasons and unhandledErrors, so --json output and reporter annotations include them (#16316)
• [jest-circus, jest-snapshot] Keep snapshot state and counts correct when a test retries (#16344)
• [@jest/create-cache-key-function] Include the caller support flags in the generated key, so a transformer that emits ESM or CJS based on them no longer shares one cache entry between the two (#16331)
• [@jest/create-cache-key-function] Include the stringified project config in the generated key, so editing a transformer's own settings invalidates what it cached (#16331)
• [@jest/transform] Include the caller support flags in a transform's cache key, so a file transformed both as ESM and as CJS no longer serves one shape's output for the other (#16331)
• [jest-config] Add missing findRelatedTests, outputFile, and replname entries to ValidConfig so they no longer trigger spurious "Unknown option" warnings (#16224)
• [jest-config] Use --config for the global config when multiple --projects are specified (#16273)
• [jest-core] Serialize bigint values in --json and --outputFile output as their literal form (4n), instead of failing the run with TypeError: Do not know how to serialize a BigInt (#16338)
• [jest-core] Do not report a CustomGC async resource (used by N-API addons such as napi-rs for per-isolate GC bookkeeping) as an open handle, since it is napi_unref'd by the addon and can never keep the event loop alive (#16379)
• [jest-each] Keep a $&, $`, $' or $$ inside a %p param value out of the replacement, so the title shows the value instead of the text around it (#16338)
• [jest-each] Interpolate a bigint into a %j title as its literal form ("4n") at any depth, instead of throwing TypeError: Do not know how to serialize a BigInt while collecting the tests (#16338)
• [jest-environment, jest-runtime] Bind sandboxInjectedGlobals to the right values when injectGlobals is false, instead of shifting every one of them by a position (#16377)
• [jest-environment-node, jest-util] Only warn about a conflicting globalsCleanup mode when one was explicitly configured, and follow the mode that is actually in effect (#16323)
• [jest-environment-node, jest-util] Stop resolving lazy globals when setting up an environment, so Node 26's builtin module globals are no longer loaded (and no longer emit their deprecation warnings) for every test file (#16324)
• [jest-haste-map] Keep watch mode alive when an outside process briefly makes a file unreadable on Windows, instead of tearing the watcher down on EPERM (#16295)
• [jest-haste-map] Keep indexing when an outside process holds a file open on Windows, instead of failing the whole crawl on EPERM (#16358)
• [jest-haste-map] Keep a duplicated manual mock resolving when the file it pointed at is deleted in watch mode (#16360)

... (truncated)

Commits

• 912baa3 v30.5.0
• 3aa9b8b chore: migrate CoverageReporter test off mock-fs (#16401)
• 0683cdd chore(deps): update glob to v13 (#16397)
• f7631f7 fix(jest-console): buffer console output in CustomConsole for reporters (#16155)
• d3bfe40 fix(reporters): enforce 80 column limit fallback for coverage table i… (#16227)
• b614603 feat(@​jest/source-map): replace source-map-support with a Jest-owned implem...
• a189ce0 fix(jest-message-util): print inner errors of AggregateError test failures (#...
• 01e18c6 chore: update some more deps (#16299)
• 8148106 chore: fix lint errors
• b91717a chore: refresh coding agent instructions (#16182)
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Assignees

The following users could not be added as assignees: ynahmany. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

Please fix the above issues or remove invalid values from dependabot.yml.

[maxigimenez]

Security dependency triage — Tier B, needs a decision. Not auto-mergeable.

What and why. @jest/reporters 30.4.1 → 30.5.0 in both packages/cmd and packages/jest (devDependencies). Closes no Vanta finding and no advisory — npm audit --package-lock-only on main (99d37d4) reports only @humanfs/node, @vitest/mocker, vitest and esbuild. Routine minor bump, not a security fix.

Exposure. development. Both entries are devDependencies; the reporters package is used to run the suites, not shipped.

The fix. Three files: package-lock.json, packages/cmd/package.json, packages/jest/package.json (+1369 / −181).

Why Tier B. Same-major minor and dev-scope, but the lockfile diff is far past the Tier A ceiling of 3 top-level stanzas:

• 35 top-level lockfile stanzas appear in the hunks.
• It pulls in a whole new native-binary family — @parcel/watcher plus 12 platform packages (@parcel/watcher-linux-x64-glibc, -darwin-arm64, -win32-x64, …) and node-addon-api. jest 30.5.0 replaces the hand-rolled NodeWatcher/FSEventsWatcher with @parcel/watcher (jestjs/jest#16188), so this is expected, but new prebuilt native binaries on every supported platform are not a rubber-stamp change.
• It strips "peer": true from 26 stanzas (including the @rolldown/binding-* family), which is lockfile churn unrelated to the named bump — the same churn flagged on [CSR-0] chore: Bump @jest/types from 30.4.1 to 30.5.0 #411 and [CSR-0] chore: Bump eslint-plugin-turbo from 2.8.20 to 2.10.12 #415.
• Two manifests.

Breaking-change check. The upstream release notes open with, verbatim: "This is a big release. It touches jest-runtime, jest-resolve and jest-haste-map in many places, and with this many changes there might be regressions 😬." They also ask maintainers to run suites with --no-watchman to exercise the new crawler. glob goes to v13 and babel-plugin-istanbul to v8 inside the release. That is an explicit regression warning in range, which is a Tier A disqualifier on its own.

Verification. npm ci --dry-run at head 4d2c8df succeeds — unlike #416/#417/#418, this PR's lockfile is in sync with its manifests.

CI coverage. No workflow is paths-filtered, so all trigger. Checks on 4d2c8df are green: lint, Unit Tests, cmd Types, jest Types, typecheck-status, matrix (run 33399514078). Green CI is why this is Tier B rather than Tier C — the diff shape and the upstream regression warning are what hold it back, not a failure.

What a human should still check.

1. The new @parcel/watcher native dependency across the platforms the team builds and tests on — a prebuilt binary that fails to resolve shows up as a broken install, not a test failure.
2. Whether the "peer": true removals across 26 stanzas are intended. They recur on [CSR-0] chore: Bump @jest/types from 30.4.1 to 30.5.0 #411 and [CSR-0] chore: Bump eslint-plugin-turbo from 2.8.20 to 2.10.12 #415, which suggests the lockfile drifts whenever Dependabot regenerates it, and it would be worth fixing once at the source rather than reviewing it on each PR.
3. Run the suite once with --no-watchman, as the release notes request.

Needs release. No.

---

Generated by Claude Code