jest-mock
30.5.2 · 18 Sep 2026MIT94.8M / weekRepositoryHomepagenpmAtom feed
Upgrading jest-mock From 24.0.0 to 24.9.0
6 releases in betweenevery note read
- 2
- changes to make
- 0
- advisories fixed
- 74
- new
- 54
- fixes
Before you upgrade
Tick each one off as you go- Breaking24.7.0
- Breaking24.3.0
Security
- 24.3.0
jest-cli: Fix prototype pollution vulnerability in dependency
Release by release
- New
expect: Highlight substring differences when matcher fails, part 1
- New
expect: Highlight substring differences when matcher fails, part 2
- New
expect: Improve report when mock-spy matcher fails, part 1
- New
expect: Improve report when mock-spy matcher fails, part 2
- New
- New
jest-circus: Bind to Circus events via an optional event handler on any custom env
- New
expect: Improve report when matcher fails, part 15
- New
jest-cli: Update
--forceExitand "did not exit for one second" message colors - New
expect: Improve report when matcher fails, part 16
- New
- Breaking
expect: Remove repetition of matcherName and options in matchers
- New
@jest/core, @jest/test-sequencer: Move
testSequencerto individual package@jest/test-sequencer - New
@jest/core, jest-cli, jest-config: Add option
testSequencerallow user use custom sequencer. - New
expect: Add negative equality tests for iterables
- Fixed
jest-haste-map: Resolve fs watcher EMFILE error
- Breaking
- New
: Improve report when matcher fails, part 13
- New
@jest/core: Filter API pre-filter setup hook
- New
jest-snapshot: Improve report when matcher fails, part 14
- New
@jest/reporter: Display todo and skip test descriptions when verbose is true
- New
- New
jest-haste-map: Expose
throwOnModuleCollisionviaconfig.haste
- New
- Security
jest-cli: Fix prototype pollution vulnerability in dependency
- Breaking
expect: Remove duck typing and obsolete browser support code when comparing DOM nodes and use DOM-Level-3 API instead
- New
: Improve report when matcher fails, part 10
- New
: Improve report when matcher fails, part 11
- Security
51 internal lines (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.