jest-diff

What is jest-diff?

The jest-diff npm package is a utility primarily used to show differences between two values, typically used in testing environments to assert the equality of objects, arrays, or other data structures. It is part of the Jest testing framework but can be used independently for its diffing capabilities.

What are jest-diff's main functionalities?

Diffing two values

This feature allows you to compare two JavaScript objects and outputs a string that visually represents the differences between them. It is useful for debugging and in test assertions to see what exactly differs when a test fails.

const diff = require('jest-diff');
const a = { a: { b: { c: 5 } } };
const b = { a: { b: { c: 6 } } };
console.log(diff(a, b));

Customizing diff output

This feature allows customization of the diff output by passing options. You can specify annotations for the compared values, which helps in making the output more understandable and tailored to specific needs.

const diff = require('jest-diff');
const options = { aAnnotation: 'First', bAnnotation: 'Second' };
const a = [1, 2, 3];
const b = [2, 1, 3];
console.log(diff(a, b, options));

Other packages similar to jest-diff

deep-diff

Deep-diff is a library that provides a detailed analysis of differences between any two JavaScript objects. It is more granular than jest-diff as it provides more detailed information about the type of change (edit, delete, add), which can be useful for more complex diffing needs.

diff

The 'diff' package is another popular choice for computing differences between texts. It is not limited to JavaScript objects and can handle strings effectively, making it suitable for applications like text editors or any scenario where text comparison is needed. Unlike jest-diff, it does not provide a structured view for object differences.

README

jest-diff

Display differences clearly so people can review changes confidently.

The diff named export serializes JavaScript values, compares them line-by-line, and returns a string which includes comparison lines.

Two named exports compare strings character-by-character:

• diffStringsUnified returns a string.
• diffStringsRaw returns an array of Diff objects.

Three named exports compare arrays of strings line-by-line:

• diffLinesUnified and diffLinesUnified2 return a string.
• diffLinesRaw returns an array of Diff objects.

Installation

To add this package as a dependency of a project, run either of the following commands:

• npm install jest-diff
• yarn add jest-diff

Usage of diff()

Given JavaScript values, diff(a, b, options?) does the following:

• serialize the values as strings using the pretty-format package
• compare the strings line-by-line using the diff-sequences package
• format the changed or common lines using the chalk package

To use this function, write either of the following:

• const {diff} = require('jest-diff'); in CommonJS modules
• import {diff} from 'jest-diff'; in ECMAScript modules

Example of diff()

const a = ['delete', 'common', 'changed from'];
const b = ['common', 'changed to', 'insert'];

const difference = diff(a, b);

The returned string consists of:

• annotation lines: describe the two change indicators with labels, and a blank line
• comparison lines: similar to “unified” view on GitHub, but Expected lines are green, Received lines are red, and common lines are dim (by default, see Options)

- Expected
+ Received

  Array [
-   "delete",
    "common",
-   "changed from",
+   "changed to",
+   "insert",
  ]

Edge cases of diff()

Here are edge cases for the return value:

• ' Comparing two different types of values. …' if the arguments have different types according to the jest-get-type package (instances of different classes have the same 'object' type)
• 'Compared values have no visual difference.' if the arguments have either referential identity according to Object.is method or same serialization according to the pretty-format package
• null if either argument is a so-called asymmetric matcher in Jasmine or Jest

Usage of diffStringsUnified

Given strings, diffStringsUnified(a, b, options?) does the following:

• compare the strings character-by-character using the diff-sequences package
• clean up small (often coincidental) common substrings, also known as chaff
• format the changed or common lines using the chalk package

Although the function is mainly for multiline strings, it compares any strings.

Write either of the following:

• const {diffStringsUnified} = require('jest-diff'); in CommonJS modules
• import {diffStringsUnified} from 'jest-diff'; in ECMAScript modules

Example of diffStringsUnified

const a = 'common\nchanged from';
const b = 'common\nchanged to';

const difference = diffStringsUnified(a, b);

The returned string consists of:

• annotation lines: describe the two change indicators with labels, and a blank line
• comparison lines: similar to “unified” view on GitHub, and changed substrings have inverse foreground and background colors (that is, from has white-on-green and to has white-on-red, which the following example does not show)

- Expected
+ Received

  common
- changed from
+ changed to

Performance of diffStringsUnified

To get the benefit of changed substrings within the comparison lines, a character-by-character comparison has a higher computational cost (in time and space) than a line-by-line comparison.

If the input strings can have arbitrary length, we recommend that the calling code set a limit, beyond which splits the strings, and then calls diffLinesUnified instead. For example, Jest falls back to line-by-line comparison if either string has length greater than 20K characters.

Usage of diffLinesUnified

Given arrays of strings, diffLinesUnified(aLines, bLines, options?) does the following:

• compare the arrays line-by-line using the diff-sequences package
• format the changed or common lines using the chalk package

You might call this function when strings have been split into lines and you do not need to see changed substrings within lines.

Example of diffLinesUnified

const aLines = ['delete', 'common', 'changed from'];
const bLines = ['common', 'changed to', 'insert'];

const difference = diffLinesUnified(aLines, bLines);

- Expected
+ Received

- delete
  common
- changed from
+ changed to
+ insert

Edge cases of diffLinesUnified or diffStringsUnified

Here are edge cases for arguments and return values:

• both a and b are empty strings: no comparison lines
• only a is empty string: all comparison lines have bColor and bIndicator (see Options)
• only b is empty string: all comparison lines have aColor and aIndicator (see Options)
• a and b are equal non-empty strings: all comparison lines have commonColor and commonIndicator (see Options)

Usage of diffLinesUnified2

Given two pairs of arrays of strings, diffLinesUnified2(aLinesDisplay, bLinesDisplay, aLinesCompare, bLinesCompare, options?) does the following:

• compare the pair of Compare arrays line-by-line using the diff-sequences package
• format the corresponding lines in the pair of Display arrays using the chalk package

Jest calls this function to consider lines as common instead of changed if the only difference is indentation.

You might call this function for case insensitive or Unicode equivalence comparison of lines.

Example of diffLinesUnified2

import {format} from 'pretty-format';

const a = {
  text: 'Ignore indentation in serialized object',
  time: '2019-09-19T12:34:56.000Z',
  type: 'CREATE_ITEM',
};
const b = {
  payload: {
    text: 'Ignore indentation in serialized object',
    time: '2019-09-19T12:34:56.000Z',
  },
  type: 'CREATE_ITEM',
};

const difference = diffLinesUnified2(
  // serialize with indentation to display lines
  format(a).split('\n'),
  format(b).split('\n'),
  // serialize without indentation to compare lines
  format(a, {indent: 0}).split('\n'),
  format(b, {indent: 0}).split('\n'),
);

The text and time properties are common, because their only difference is indentation:

- Expected
+ Received

  Object {
+   payload: Object {
      text: 'Ignore indentation in serialized object',
      time: '2019-09-19T12:34:56.000Z',
+   },
    type: 'CREATE_ITEM',
  }

The preceding example illustrates why (at least for indentation) it seems more intuitive that the function returns the common line from the bLinesDisplay array instead of from the aLinesDisplay array.

Usage of diffStringsRaw

Given strings and a boolean option, diffStringsRaw(a, b, cleanup) does the following:

• compare the strings character-by-character using the diff-sequences package
• optionally clean up small (often coincidental) common substrings, also known as chaff

Because diffStringsRaw returns the difference as data instead of a string, you can format it as your application requires (for example, enclosed in HTML markup for browser instead of escape sequences for console).

The returned array describes substrings as instances of the Diff class, which calling code can access like array tuples:

The value at index 0 is one of the following:

value	named export	description
0	DIFF_EQUAL	in a and in b
-1	DIFF_DELETE	in a but not in b
1	DIFF_INSERT	in b but not in a

The value at index 1 is a substring of a or b or both.

Example of diffStringsRaw with cleanup

const diffs = diffStringsRaw('changed from', 'changed to', true);

i	diffs[i][0]	diffs[i][1]
0	0	'changed '
1	-1	'from'
2	1	'to'

Example of diffStringsRaw without cleanup

const diffs = diffStringsRaw('changed from', 'changed to', false);

i	diffs[i][0]	diffs[i][1]
0	0	'changed '
1	-1	'fr'
2	1	't'
3	0	'o'
4	-1	'm'

Advanced import for diffStringsRaw

Here are all the named imports that you might need for the diffStringsRaw function:

• const {DIFF_DELETE, DIFF_EQUAL, DIFF_INSERT, Diff, diffStringsRaw} = require('jest-diff'); in CommonJS modules
• import {DIFF_DELETE, DIFF_EQUAL, DIFF_INSERT, Diff, diffStringsRaw} from 'jest-diff'; in ECMAScript modules

To write a formatting function, you might need the named constants (and Diff in TypeScript annotations).

If you write an application-specific cleanup algorithm, then you might need to call the Diff constructor:

const diffCommon = new Diff(DIFF_EQUAL, 'changed ');
const diffDelete = new Diff(DIFF_DELETE, 'from');
const diffInsert = new Diff(DIFF_INSERT, 'to');

Usage of diffLinesRaw

Given arrays of strings, diffLinesRaw(aLines, bLines) does the following:

• compare the arrays line-by-line using the diff-sequences package

Because diffLinesRaw returns the difference as data instead of a string, you can format it as your application requires.

Example of diffLinesRaw

const aLines = ['delete', 'common', 'changed from'];
const bLines = ['common', 'changed to', 'insert'];

const diffs = diffLinesRaw(aLines, bLines);

i	diffs[i][0]	diffs[i][1]
0	-1	'delete'
1	0	'common'
2	-1	'changed from'
3	1	'changed to'
4	1	'insert'

Edge case of diffLinesRaw

If you call string.split('\n') for an empty string:

• the result is [''] an array which contains an empty string
• instead of [] an empty array

Depending of your application, you might call diffLinesRaw with either array.

Example of split method

import {diffLinesRaw} from 'jest-diff';

const a = 'non-empty string';
const b = '';

const diffs = diffLinesRaw(a.split('\n'), b.split('\n'));

i	diffs[i][0]	diffs[i][1]
0	-1	'non-empty string'
1	1	''

Which you might format as follows:

- Expected  - 1
+ Received  + 1

- non-empty string
+

Example of splitLines0 function

For edge case behavior like the diffLinesUnified function, you might define a splitLines0 function, which given an empty string, returns [] an empty array:

export const splitLines0 = string =>
  string.length === 0 ? [] : string.split('\n');

import {diffLinesRaw} from 'jest-diff';

const a = '';
const b = 'line 1\nline 2\nline 3';

const diffs = diffLinesRaw(a.split('\n'), b.split('\n'));

i	diffs[i][0]	diffs[i][1]
0	1	'line 1'
1	1	'line 2'
2	1	'line 3'

Which you might format as follows:

- Expected  - 0
+ Received  + 3

+ line 1
+ line 2
+ line 3

In contrast to the diffLinesRaw function, the diffLinesUnified and diffLinesUnified2 functions automatically convert array arguments computed by string split method, so callers do not need a splitLine0 function.

Options

The default options are for the report when an assertion fails from the expect package used by Jest.

For other applications, you can provide an options object as a third argument:

• diff(a, b, options)
• diffStringsUnified(a, b, options)
• diffLinesUnified(aLines, bLines, options)
• diffLinesUnified2(aLinesDisplay, bLinesDisplay, aLinesCompare, bLinesCompare, options)

Properties of options object

name	default
aAnnotation	'Expected'
aColor	chalk.green
aIndicator	'-'
bAnnotation	'Received'
bColor	chalk.red
bIndicator	'+'
changeColor	chalk.inverse
changeLineTrailingSpaceColor	string => string
commonColor	chalk.dim
commonIndicator	' '
commonLineTrailingSpaceColor	string => string
compareKeys	undefined
contextLines	5
emptyFirstOrLastLinePlaceholder	''
expand	true
includeChangeCounts	false
omitAnnotationLines	false
patchColor	chalk.yellow

For more information about the options, see the following examples.

Example of options for labels

If the application is code modification, you might replace the labels:

const options = {
  aAnnotation: 'Original',
  bAnnotation: 'Modified',
};

- Original
+ Modified

  common
- changed from
+ changed to

The jest-diff package does not assume that the 2 labels have equal length.

Example of options for colors of changed lines

For consistency with most diff tools, you might exchange the colors:

import chalk from 'chalk';

const options = {
  aColor: chalk.red,
  bColor: chalk.green,
};

Example of option for color of changed substrings

Although the default inverse of foreground and background colors is hard to beat for changed substrings within lines, especially because it highlights spaces, if you want bold font weight on yellow background color:

import chalk from 'chalk';

const options = {
  changeColor: chalk.bold.bgYellowBright,
};

Example of option to format trailing spaces

Because diff() does not display substring differences within lines, formatting can help you see when lines differ by the presence or absence of trailing spaces found by /\s+$/ regular expression.

• If change lines have a background color, then you can see trailing spaces.
• If common lines have default dim color, then you cannot see trailing spaces. You might want yellowish background color to see them.

const options = {
  aColor: chalk.rgb(128, 0, 128).bgRgb(255, 215, 255), // magenta
  bColor: chalk.rgb(0, 95, 0).bgRgb(215, 255, 215), // green
  commonLineTrailingSpaceColor: chalk.bgYellow,
};

The value of a Color option is a function, which given a string, returns a string.

If you want to replace trailing spaces with middle dot characters:

const replaceSpacesWithMiddleDot = string => '·'.repeat(string.length);

const options = {
  changeLineTrailingSpaceColor: replaceSpacesWithMiddleDot,
  commonLineTrailingSpaceColor: replaceSpacesWithMiddleDot,
};

If you need the TypeScript type of a Color option:

import {DiffOptionsColor} from 'jest-diff';

Example of options for no colors

To store the difference in a file without escape codes for colors, provide an identity function:

const noColor = string => string;

const options = {
  aColor: noColor,
  bColor: noColor,
  changeColor: noColor,
  commonColor: noColor,
  patchColor: noColor,
};

Example of options for indicators

For consistency with the diff command, you might replace the indicators:

const options = {
  aIndicator: '<',
  bIndicator: '>',
};

The jest-diff package assumes (but does not enforce) that the 3 indicators have equal length.

Example of options to limit common lines

By default, the output includes all common lines.

To emphasize the changes, you might limit the number of common “context” lines:

const options = {
  contextLines: 1,
  expand: false,
};

A patch mark like @@ -12,7 +12,9 @@ accounts for omitted common lines.

Example of option for color of patch marks

If you want patch marks to have the same dim color as common lines:

import chalk from 'chalk';

const options = {
  expand: false,
  patchColor: chalk.dim,
};

Example of option to include change counts

To display the number of changed lines at the right of annotation lines:

const a = ['common', 'changed from'];
const b = ['common', 'changed to', 'insert'];

const options = {
  includeChangeCounts: true,
};

const difference = diff(a, b, options);

- Expected  - 1
+ Received  + 2

  Array [
    "common",
-   "changed from",
+   "changed to",
+   "insert",
  ]

Example of option to omit annotation lines

To display only the comparison lines:

const a = 'common\nchanged from';
const b = 'common\nchanged to';

const options = {
  omitAnnotationLines: true,
};

const difference = diffStringsUnified(a, b, options);

  common
- changed from
+ changed to

Example of option for empty first or last lines

If the first or last comparison line is empty, because the content is empty and the indicator is a space, you might not notice it.

The replacement option is a string whose default value is '' empty string.

Because Jest trims the report when a matcher fails, it deletes an empty last line.

Therefore, Jest uses as placeholder the downwards arrow with corner leftwards:

const options = {
  emptyFirstOrLastLinePlaceholder: '↵', // U+21B5
};

If a content line is empty, then the corresponding comparison line is automatically trimmed to remove the margin space (represented as a middle dot below) for the default indicators:

Indicator	untrimmed	trimmed
aIndicator	'-·'	'-'
bIndicator	'+·'	'+'
commonIndicator	' ·'	''

Example of option for sorting object keys

When two objects are compared their keys are printed in alphabetical order by default. If this was not the original order of the keys the diff becomes harder to read as the keys are not in their original position.

Use compareKeys to pass a function which will be used when sorting the object keys.

const a = {c: 'c', b: 'b1', a: 'a'};
const b = {c: 'c', b: 'b2', a: 'a'};

const options = {
  // The keys will be in their original order
  compareKeys: () => 0,
};

const difference = diff(a, b, options);

- Expected
+ Received

  Object {
    "c": "c",
-   "b": "b1",
+   "b": "b2",
    "a": "a",
  }

Depending on the implementation of compareKeys any sort order can be used.

const a = {c: 'c', b: 'b1', a: 'a'};
const b = {c: 'c', b: 'b2', a: 'a'};

const options = {
  // The keys will be in reverse order
  compareKeys: (a, b) => (a > b ? -1 : 1),
};

const difference = diff(a, b, options);

- Expected
+ Received

  Object {
    "a": "a",
-   "b": "b1",
+   "b": "b2",
    "c": "c",
  }

Changelog

30.0.0

Features

• [*] Renamed globalsCleanupMode to globalsCleanup and --waitNextEventLoopTurnForUnhandledRejectionEvents to --waitForUnhandledRejections
• [expect] Add ArrayOf asymmetric matcher for validating array elements. (#15567)
• [babel-jest] Add option excludeJestPreset to allow opting out of babel-preset-jest (#15164)
• [expect] Revert #15038 to fix expect(fn).toHaveBeenCalledWith(expect.objectContaining(...)) when there are multiple calls (#15508)
• [jest-circus, jest-cli, jest-config] Add waitNextEventLoopTurnForUnhandledRejectionEvents flag to minimise performance impact of correct detection of unhandled promise rejections introduced in #14315 (#14681)
• [jest-circus] Add a waitBeforeRetry option to jest.retryTimes (#14738)
• [jest-circus] Add a retryImmediately option to jest.retryTimes (#14696)
• [jest-circus, jest-jasmine2] Allow setupFilesAfterEnv to export an async function (#10962)
• [jest-circus, jest-test-result] Add startedAt timestamp in TestCaseResultObject within onTestCaseResult (#15145)
• [jest-cli] Export buildArgv (#15310)
• [jest-config] [BREAKING] Add mts and cts to default moduleFileExtensions config (#14369)
• [jest-config] [BREAKING] Update testMatch and testRegex default option for supporting mjs, cjs, mts, and cts (#14584)
• [jest-config] Loads config file from provided path in package.json (#14044)
• [jest-config] Allow loading jest.config.cts files (#14070)
• [jest-config] Show rootDir in error message when a preset fails to load (#15194)
• [jest-config] Support loading TS config files using esbuild-register via docblock loader (#15190)
• [jest-config] Allow passing TS config loader options via docblock comment (#15234)
• [jest-config] If Node is running with type stripping enabled, do not require a TS loader (#15480)
• [@jest/core] Group together open handles with the same stack trace (#13417, & #14789)
• [@jest/core] Add perfStats to surface test setup overhead (#14622)
• [@jest/core] [BREAKING] Changed --filter to accept an object with shape { filtered: Array<string> } to match documentation (#13319)
• [@jest/core] Support --outputFile option for --listTests (#14980)
• [@jest/core] Stringify Errors properly with --json flag (#15329)
• [@jest/core, @jest/test-sequencer] [BREAKING] Exposes globalConfig & contexts to TestSequencer (#14535, & #14543)
• [jest-each] Introduce %$ option to add number of the test to its title (#14710)
• [@jest/environment] [BREAKING] Remove deprecated jest.genMockFromModule() (#15042)
• [@jest/environment] [BREAKING] Remove unnecessary defensive code (#15045)
• [jest-environment-jsdom] [BREAKING] Upgrade JSDOM to v22 (#13825)
• [@jest/environment-jsdom-abstract] Introduce new package which abstracts over the jsdom environment, allowing usage of custom versions of JSDOM (#14717)
• [jest-environment-node] Update jest environment with dispose symbols Symbol (#14888 & #14909)
• [expect, @jest/expect] [BREAKING] Add type inference for function parameters in CalledWith assertions (#15129)
• [@jest/expect-utils] Properly compare all types of TypedArrays (#15178)
• [@jest/fake-timers] [BREAKING] Upgrade @sinonjs/fake-timers to v13 (#14544 & #15470)
• [@jest/fake-timers] Exposing new modern timers function advanceTimersToFrame() which advances all timers by the needed milliseconds to execute callbacks currently scheduled with requestAnimationFrame (#14598)
• [jest-matcher-utils] Add SERIALIZABLE_PROPERTIES to allow custom serialization of objects (#14893)
• [jest-mock] Add support for the Explicit Resource Management proposal to use the using keyword with jest.spyOn(object, methodName) (#14895)
• [jest-reporters] Add support for DEC mode 2026 (#15008)
• [jest-resolver] Support file:// URLs as paths (#15154)
• [jest-resolve,jest-runtime,jest-resolve-dependencies] Pass the conditions when resolving stub modules (#15489)
• [jest-runtime] Exposing new modern timers function jest.advanceTimersToFrame() from @jest/fake-timers (#14598)
• [jest-runtime] Support import.meta.filename and import.meta.dirname (available from Node 20.11) (#14854)
• [jest-runtime] Support import.meta.resolve (#14930)
• [jest-runtime] [BREAKING] Make it mandatory to pass globalConfig to the Runtime constructor (#15044)
• [jest-runtime] Add unstable_unmockModule (#15080)
• [jest-runtime] Add onGenerateMock transformer callback for auto generated callbacks (#15433 & #15482)
• [jest-runtime] [BREAKING] Use vm.compileFunction over vm.Script (#15461)
• [@jest/schemas] Upgrade @sinclair/typebox to v0.34 (#15450)
• [@jest/types] test.each(): Accept a readonly (as const) table properly (#14565)
• [@jest/types] Improve argument type inference passed to test and describe callback functions from each tables (#14920)
• [jest-snapshot] [BREAKING] Add support for Error causes in snapshots (#13965)
• [jest-snapshot] Support Prettier 3 (#14566)
• [@jest/util-snapshot] Extract utils used by tooling from jest-snapshot into its own package (#15095)
• [pretty-format] [BREAKING] Do not render empty string children ('') in React plugin (#14470)

Fixes

• [expect] Show AggregateError to display (#15346)
• [*] Replace exit with exit-x (#15399)
• [babel-plugin-jest-hoist] Use denylist instead of the deprecated blacklist for Babel 8 support (#14109)
• [babel-plugin-jest-hoist] Do not rely on buggy Babel behaviour (#15415)
• [expect] Check error instance type for toThrow/toThrowError (#14576)
• [expect] Improve diff for failing expect.objectContaining (#15038)
• [expect] Use Array.isArray to check if an array is an Array (#15101)
• [expect] Fix Error cause assertion errors (#15339)
• [jest-changed-files] Print underlying errors when VCS commands fail (#15052)
• [jest-changed-files] Abort sl root call if output resembles a steam locomotive (#15053)
• [jest-circus] [BREAKING] Prevent false test failures caused by promise rejections handled asynchronously (#14315)
• [jest-circus] Replace recursive makeTestResults implementation with iterative one (#14760)
• [jest-circus] Omit expect.hasAssertions() errors if a test already has errors (#14866)
• [jest-circus, jest-expect, jest-snapshot] Pass test.failing tests when containing failing snapshot matchers (#14313)
• [jest-circus] Concurrent tests now emit jest circus events at the correct point and in the expected order. (#15381)
• [jest-cli] [BREAKING] Validate CLI flags that require arguments receives them (#14783)
• [jest-config] Make sure to respect runInBand option (#14578)
• [jest-config] Support testTimeout in project config (#14697)
• [jest-config] Support coverageReporters in project config (#14697)
• [jest-config] Allow reporters in project config (#14768)
• [jest-config] Allow Node16/NodeNext/Bundler moduleResolution in project's tsconfig (#14739)
• [@jest/create-cache-key-function] Correct the return type of createCacheKey (#15159)
• [jest-each] Allow $keypath templates with null or undefined values (#14831)
• [@jest/expect-utils] Fix comparison of DataView (#14408)
• [@jest/expect-utils] [BREAKING] exclude non-enumerable in object matching (#14670)
• [@jest/expect-utils] Fix comparison of URL (#14672)
• [@jest/expect-utils] Check Symbol properties in equality (#14688)
• [@jest/expect-utils] Catch circular references within arrays when matching objects (#14894)
• [@jest/expect-utils] Fix not addressing to Sets and Maps as objects without keys (#14873)
• [jest-haste-map] Fix errors or clobbering with multiple hasteImplModulePaths (#15522)
• [jest-leak-detector] Make leak-detector more aggressive when running GC (#14526)
• [jest-runtime] Properly handle re-exported native modules in ESM via CJS (#14589)
• [jest-runtime] Refactor _importCoreModel so required core module is consistent if modified while loading (#15077)
• [jest-schemas, jest-types] [BREAKING] Fix type of testFailureExitCode config option(#15232)
• [jest-util] Make sure isInteractive works in a browser (#14552)
• [pretty-format] [BREAKING] Print ArrayBuffer and DataView correctly (#14290)
• [pretty-format] Fixed a bug where "anonymous custom elements" were not being printed as expected. (#15138)
• [jest-cli] When specifying paths on the command line, only match against the relative paths of the test files (#12519)
  • [BREAKING] Changes testPathPattern configuration option to testPathPatterns, which now takes a list of patterns instead of the regex.
  • [BREAKING] --testPathPattern is now --testPathPatterns
  • [BREAKING] Specifying testPathPatterns when programmatically calling watch must be specified as new TestPathPatterns(patterns), where TestPathPatterns can be imported from @jest/pattern
• [jest-reporters, jest-runner] Unhandled errors without stack get correctly logged to console (#14619)
• [jest-util] Always load mjs files with import (#15447)
• [jest-worker] Properly handle a circular reference error when worker tries to send an assertion fails where either the expected or actual value is circular (#15191)
• [jest-worker] Properly handle a BigInt when worker tries to send an assertion fails where either the expected or actual value is BigInt (#15191)
• [expect] Resolve issue where ObjectContaining matched non-object values. ([#15463])(https://github.com/jestjs/jest/pull/15463).
  • Adds a conditional/check to ensure the argument passed to expect is an object.
  • Add unit tests for new ObjectContaining behavior.
  • Remove invalid/wrong test case assertions for ObjectContaining.
• [jest-worker] Addresses incorrect state on exit (#15610)

Performance

• [*] [BREAKING] Bundle all of Jest's modules into index.js (#12348, #14550 & #14661)
• [jest-haste-map] Only spawn one process to check for watchman installation (#14826)
• [jest-runner] Better cleanup source-map-support after test to resolve (minor) memory leak (#15233)
• [jest-circus, jest-environment-node, jest-repl, jest-runner, jest-util] Cleanup global variables on environment teardown to reduce memory leaks (#15215 & #15636 & #15643)

Chore & Maintenance

• [jest-environment-jsdom, jest-environment-jsdom-abstract] Increased version of jsdom to ^26.0.0 (#15325CVE-2024-37890)
• [*] Increase version of micromatch to ^4.0.7 (#15082)
• [*] [BREAKING] Drop support for Node.js versions 14, 16, 19, 21 and 23 (#14460, #15118, #15623, #15640)
• [*] [BREAKING] Drop support for typescript@4.3, minimum version is now 5.4 (#14542, #15621)
• [*] Depend on exact versions of monorepo dependencies instead of ^ range (#14553)
• [*] [BREAKING] Add ESM wrapper for all of Jest's modules (#14661)
• [*] [BREAKING] Upgrade to glob@10 (#14509)
• [*] Use TypeError over Error where appropriate (#14799)
• [docs] Fix typos in CHANGELOG.md and packages/jest-validate/README.md (#14640)
• [docs] Don't use alias matchers in docs (#14631)
• [babel-jest, babel-preset-jest] [BREAKING] Increase peer dependency of @babel/core to ^7.11 (#14109)
• [babel-jest, @jest/transform] Update babel-plugin-istanbul to v6 (#15156)
• [babel-plugin-jest-hoist] Move unnecessary dependencies to devDependencies (#15010)
• [expect] [BREAKING] Remove .toBeCalled(), .toBeCalledTimes(), .toBeCalledWith(), .lastCalledWith(), .nthCalledWith(), .toReturn(), .toReturnTimes(), .toReturnWith(), .lastReturnedWith(), .nthReturnedWith() and .toThrowError() matcher aliases (#14632)
• [jest-cli, jest-config, @jest/types] [BREAKING] Remove deprecated --init argument (#14490)
• [jest-config, @jest/core, jest-util] Upgrade ci-info (#14655)
• [jest-mock] [BREAKING] Remove MockFunctionMetadataType, MockFunctionMetadata and SpyInstance types (#14621)
• [@jest/reporters] Upgrade istanbul-lib-source-maps (#14924)
• [jest-schemas] Upgrade @sinclair/typebox (#14775)
• [jest-transform] Upgrade write-file-atomic (#14274)
• [jest-util] Upgrade picomatch to v4 (#14653 & #14885)
• [docs] Append to NODE_OPTIONS, not overwrite ([#14730](https://github.com/jestjs/jest/pull/14730))
• [docs] Updated .toHaveBeenCalled() documentation to correctly reflect its functionality (#14842)
• [docs] Link NestJS documentation on testing with Jest (#14940)
• [docs] Revised documentation for .toHaveBeenCalled() to accurately depict its functionality. (#14853)
• [docs] Removed ExpressJS reference link from documentation due to dead link (#15270)
• [docs] Correct broken links in docs (#15359)