@jest/environment
30.5.2 · 18 Sep 2026MIT80.2M / weekRepositoryHomepagenpmAtom feed
Upgrading @jest/environment From 30.5.0 to 30.5.1
1 release in betweenevery note read
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 5
- fixes
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
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.