jest v30.5.1

v30.5.1
Changed 1
  • Name the testEnvironmentOptions.globalsCleanup option and link the docs from the JEST-01 deprecation warning
Fixed 5
  • Don't warn about global-only options in the config that supplies the global config
  • Stop accepting reporters, coverageReporters, workerIdleMemoryLimit, cwd and runnerOptions in a project config
  • Warn about maxWorkers and coverageThreshold in a project config instead of dropping them without warning
  • Match moduleNameMapper patterns against the specifier as written again
  • Resolve package imports specifiers like #dep under ESM again

From jest

Fixes
  • [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 --projects when no root config is passed (#16411)
  • [jest-config, jest-types] Stop accepting reporters, coverageReporters, workerIdleMemoryLimit, cwd and runnerOptions in a project config - they were silently ignored, and now warn like the other global-only options (#16411)
  • [jest-config, jest-validate] Warn about maxWorkers and coverageThreshold in a project config instead of dropping them without a word (#16411)
  • [jest-resolve] Match moduleNameMapper patterns against the specifier as written again (reverting #16390) (#16417)
  • [jest-runtime] Resolve package imports specifiers like #dep under ESM again (#16413)
Chore & Maintenance
  • [jest-util] Name the testEnvironmentOptions.globalsCleanup option and link the docs from the JEST-01 deprecation warning, and document the option's modes (#16404)
New Contributors

Full Changelog: https://github.com/jestjs/jest/compare/v30.5.0...v30.5.1

View original

Upgraded? How did it go?

Discussion