jest-util
30.5.1 · 1 Sep 2026MIT156.2M / weekRepositoryHomepagenpmAtom feed
Upgrading jest-util From 30.4.0 to 30.5.1
3 releases in betweenevery note read
Reading releases, release notes and advisories…
- 2
- changes to make
- 0
- advisories fixed
- 36
- new
- 92
- fixes
Before you upgrade
Tick each one off as you go- breaking30.5.0
- deprecated30.5.0
Release by release
- fixed
jest-config: Don't warn about global-only options in the config that supplies the global config - the root config a project resolves to, or the first entry of
--projectswhen no root config is passed - fixed
jest-config, jest-types: Stop accepting
reporters,coverageReporters,workerIdleMemoryLimit,cwdandrunnerOptionsin a project config - they were silently ignored, and now warn like the other global-only options - fixed
jest-config, jest-validate: Warn about
maxWorkersandcoverageThresholdin a project config instead of dropping them without a word - fixed
jest-resolve: Match
moduleNameMapperpatterns against the specifier as written again (reverting #16390) - fixed
jest-runtime: Resolve package
importsspecifiers like#depunder ESM again
- fixed
- breaking
jest-haste-map: Match watched files on a full extension, so
moduleFileExtensions: ['js']no longer acceptsfoo.mjs - deprecated
@jest/source-map: Deprecate
getCallsitein favour ofSourceMapSupport#getCallsite - new
babel-plugin-istanbulis updated to v8 - new
globis updated to v13
- breaking
- new
[jest-config, jest-core, jest-runner, jest-schemas, jest-types]Allow custom runner configuration options via tuple format['runner-path', {options}] - fixed
jest-runtime: Align CJS-from-ESM default export with Node:
module.exportsis always the ESM default,__esModuleunwrapping is no longer applied
- new
17 internal lines (docs, tests, tooling) left out.