v6.4.2

Compare Source

Bug Fixes

• Remove errant export of GetByRoleMatcher, fixing type checking in some TS configurations (#​575) (a93c0c4)

v6.4.1

Compare Source

Bug Fixes

• Export type TestingLibraryMatchers from "./matchers" (#​576) (dd1c4dd)

v6.4.0

Compare Source

Features

• Add toHaveRole matcher (#​572) (f7dc673)

v6.3.0

Compare Source

Features

• Support for regular expressions in toHaveClass (#​563) (9787ed5)

v6.2.1

Compare Source

Bug Fixes

• Standalone types for "./matchers" export and add Bun support (#​566) (5675b86)

v6.2.0

Compare Source

Features

• toHaveAccessibleDescription supports aria-description (#​565) (1fb156c)

v6.1.6

Compare Source

Bug Fixes

• Upgrade @​adobe/css-tools to v4.3.2 (#​553) (b64b953)

v6.1.5

Compare Source

Bug Fixes

• support uppercase custom props in toHaveStyle (#​552) (b7b7c6a)

v6.1.4

Compare Source

Bug Fixes

• upgrade @adobe/css-tools to 4.3.1 to address vulnerability (#​532) (44f1eab)

v6.1.3

Compare Source

Bug Fixes

• proper @​jest/globals import (#​530) (5b492ac)

v6.1.2

Compare Source

Bug Fixes

• bump @​adobe/css-tools for ESM support (#​525) (b959a68)

v6.1.1

Compare Source

Bug Fixes

• package.json: update main and module file paths (#​523) (853a3e5)

v6.1.0

Compare Source

Features

• Publish ESM and CJS (https://github.com/testing-library/jest-dom/pull/519)

v6.0.1

Compare Source

Bug Fixes

• matchers type is making the global expect unsafe (#​513) (bdb34f1)

v6.0.0

Compare Source

Features

• local types, supporting jest, @​jest/globals, vitest (#​511) (4b764b9)

BREAKING CHANGES

• Removes the extend-expect script. Users should use
  the default import path or one of the new test platform-specific
  paths to automatically extend the appropriate "expect" instance.

extend-expect was not documented in the Readme, so this change should
have minimal impact.

Users can now use the following import paths to automatically extend
"expect" for their chosen test platform:

• @​testing-library/jest-dom - jest (@​types/jest)
• @​testing-library/jest-dom/jest-globals - @​jest/globals
• @​testing-library/jest-dom/vitest - vitest

For example:

import '@​testing-library/jest-dom/jest-globals'

Importing from one of the above paths will augment the appropriate
matcher interface for the given test platform, assuming the import
is done in a .ts file that is included in the user's tsconfig.json.

It's also (still) possible to import the matchers directly without
side effects:

import * as matchers from '@​testing-library/jest-dom/matchers'

• Update kcd-scripts
• Drop node < 14

v5.17.0

Compare Source

Features

• New toHaveAccessibleErrorMessage better implementing the spec, deprecate toHaveErrorMessage (#​503) (d717c66)