Cannot find module '@testing-library/jest-dom/matchers'

[nharrisanalyst]

I am getting the error

Cannot find module '@testing-library/jest-dom/matchers' from 'selector.test.js'

are the docs correct it seems to work when I do
import {
toBeInTheDocument
} from '@testing-library/jest-dom

[gnapse]

Indeed. It seems we messed up when switching to v5. It's not enough to put a matchers.js file at the root. We also need to list it in the files entry of package.json, and not sure if that's enough.

[jgoz]

Adding it to files should be enough to make it work for JS users. There are no type definitions for jest-dom/matchers, so it will continue not working for TS users until someone adds them to DT.

[gnapse]

I wonder if, in addition to add it to files, we also need to stop using import and go back to require. Asking because I see that the root extend-expect.js does that when importing (or rather requiring) the corresponding extend-expect.js from inside src/.

[jgoz]

I think they can be left as import statements inside of src, but the matchers.js file itself should probably use require. It should also import the files from dist instead of src. And it should re-export using module.exports.

[gnapse]

I created #200 to tackle this. Tried those changes locally in a playground repo that uses jest-dom by selectively importing custom matchers and extending expect manually, and it works, whereas I confirmed it does not work with these changes in place, as @nharrisanalyst reported.

[gnapse]

🎉 This issue has been resolved in version 5.1.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀