`require-hook` rule checks non-test files

Hello, first of all: thanks for your work!

I’m currently facing an issue upgrading to v25.0.1 due to the require-hook rule. This rule is applied outside of test files.

Here’s an example with .tsx and ts files:

Versions:

• eslint: 7.32.0
• eslint-plugin-jest: 25.0.1
• node: 14.17.0

Thank’s for your help!

[SimenB]

@thibaultdelor unfortunately not as config Jest’s config loading is async while ESLint’s config loading is sync. See https://github.com/jest-community/eslint-plugin-jest/pull/754#issuecomment-780396777 for details

---

@G-Rath we should probably add an example to the docs as this rule is quite aggressive and seemingly the only one we have that causes issues in this way (at least in recommended config) - this is the third issue about it in as many days.

[G-Rath]

fwiw, this rule isn’t in the recommended config, but 💯 agree on having this in our docs.

tbh I actually thought we did mention it in the readme but we don’t so I think that should definitely change - I think our general configuration example should be using overrides with Jest’s default file matcher as the glob (or as close to as possible).

Then for require-hook I think we should be good to just have an extra warning saying this rule is very noisy, make sure you're using overrides to only apply it to your test files as shown [in the readme](link)