@jest/environment
30.5.2 · 18 Sep 2026MIT80.2M / weekRepositoryHomepagenpmAtom feed
Upgrading @jest/environment From 30.5.0 to 30.5.2
2 releases in betweenevery note read
Release by release
- New
@jest/transform: Strip TypeScript types with Node when no transformer claims a
.ts,.mtsor.ctsfile - Fixed
jest-core, jest-haste-map, jest-transform: Keep
require('../package.json')external when bundling, sojest --versionand the transform and haste-map cache keys report the released version instead of the previous one - Fixed
jest-each: Escape a table row's keys before building the
$variableinterpolationRegExp, so a column name such ascount(*)no longer fails the whole table withInvalid regular expression, and a.or|in a column name is matched literally - Fixed
@jest/source-map: Resolve absolute Windows paths in a source map's
sourcesandsourceRootagain, instead of appending them to the transformed file's directory
- New
- 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
1 internal line (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.