Update Dev dependencies (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
jest-fetch-mock	3.2.0 → 4.2.0
typescript (source)	6.0.3 → 7.0.2

---

Release Notes

jefflau/jest-fetch-mock (jest-fetch-mock)

v4.2.0

Compare Source

Added

• Route-based mocking (#​171): fetchMock.route(urlOrPredicate, bodyOrFunction?, init?) and routeOnce(...) register matcher→response pairs that coexist, plus clearRoutes(). First registered match serves. Precedence: queued once-responses > routes > the conditional gate and ambient mockResponse; a matching route fires even under dontMock() (mock only known endpoints, let the rest hit the network); mockReject/mockAbort override routes. resetMocks() clears routes.

v4.1.0

Compare Source

Added

• fetchMock.Response.redirect(), .error() and (on native fetch) .json() statics are exposed through the Response wrapper (#​191)

Docs

• README fully aligned with 4.0 (native-primitives intro, setupFilesAfterEnv one-liner as the primary setup, rewritten resetMocks note around the auto-re-arm, self-contained types, redirected mocking works everywhere, realFetch in examples)

v4.0.0

Compare Source

The modernization release (published as 4.0.0-beta.1 earlier the same day; identical content). Headline: jest-fetch-mock no longer replaces the global fetch classes with node-fetch implementations.

Changed (breaking)

• Native fetch primitives. In environments that provide fetch/Response/Request/Headers (jest-environment-node has since Jest 28), the mock builds on them and never replaces them — fixing the whole "the global Response broke my unrelated test" cluster (#​218) and making instanceof, streams, FormData, and Response.json() behave natively. Where the environment has none (jest-environment-jsdom), the cross-fetch fallback engages exactly as before, filling only the missing globals.
• disableMocks() restores the environment's original fetch (previously it installed cross-fetch's).
• Support floor: Node ≥ 18, Jest ≥ 28. The 3.x line remains available for older stacks.
• TypeScript definitions are self-contained: no @types/jest requirement (works with @jest/globals-only setups, #​248) and no forced dom lib (#​201). Ambient Response/Request types must come from your lib: ["dom"] or @types/node ≥ 18 — in practice, every Jest project has one of these.
• Relative URL inputs in native mode resolve against http://localhost/ for matching purposes (the native Request requires absolute URLs); jsdom-fallback behavior is unchanged.
• domexception dependency removed (native since Node 17).

Added

• createFetchMock(jest) factory, also available from the dependency-free entry jest-fetch-mock/factory — build an instance with an explicitly-passed jest object, for injectGlobals: false / @jest/globals setups.
• "setupFiles": ["jest-fetch-mock/setup"] one-liner setup.
• resetMocks: true auto-re-arm (#​78, #​81, #​202): when enableMocks() runs where beforeEach exists (setupFilesAfterEnv or a test file), the default implementation is re-armed after Jest's config-driven reset. The years-old footgun is fixed — move your setup file to setupFilesAfterEnv to benefit.
• AbortSignal.timeout() rejections carry the signal's TimeoutError; custom abort reasons pass through as-is (#​242). Plain aborts keep the historical AbortError message.
• fetchMock.defaultResponseInit — an init merged under every mocked response, e.g. default JSON headers (#​166).
• fetchMock.realFetch — the implementation unmatched requests pass through to, reassignable in tests; fetchMock.usingNativeFetch tells you which mode engaged.
• ESM wrapper and an exports map (with a ./* escape hatch so deep imports keep working); url and counter MockParams are patched onto native responses so response.url/response.redirected mocking still works.

Unchanged

Every 3.x API call, alias, chaining behavior, once-queue semantics, and the abort error message. The whole 3.x test suite and all seven consumer integration fixtures run green against 4.0.

microsoft/TypeScript (typescript)

v7.0.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: ts-jest@29.4.11
npm error Found: typescript@7.0.2
npm error node_modules/typescript
npm error   dev typescript@"7.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.3 <7" from ts-jest@29.4.11
npm error node_modules/ts-jest
npm error   dev ts-jest@"29.4.11" from the root project
npm error
npm error Conflicting peer dependency: typescript@6.0.3
npm error node_modules/typescript
npm error   peer typescript@">=4.3 <7" from ts-jest@29.4.11
npm error   node_modules/ts-jest
npm error     dev ts-jest@"29.4.11" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-07-09T06_00_47_145Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-09T06_00_47_145Z-debug-0.log