Question 1

How to set up eslint-plugin-jest with TypeScript?

Accepted Answer

Install `@typescript-eslint/parser` and configure ESLint for type-aware linting. The plugin's type-checking rules fall back safely if type information is unavailable, so it works in mixed JavaScript/TypeScript projects.

Question 2

eslint-plugin-jest or built-in Jest linting: which is better?

Accepted Answer

Jest has limited built-in linting; eslint-plugin-jest offers a comprehensive rule set for static analysis. It's better for enforcing best practices and catching errors before runtime, especially in CI/CD pipelines.

Question 3

Can I use eslint-plugin-jest with Vitest?

Accepted Answer

Yes, via the `globalPackage` setting, but the README warns there's no guarantee the semantics will hold. It's a workaround, not a fully supported integration, so expect potential mismatches.

Question 4

Why are my eslint-plugin-jest rules not applying to test files?

Accepted Answer

You likely didn't restrict the plugin to test files. Use ESLint overrides or file patterns in your config, as shown in the README, to apply rules only to files like `**/*.test.js`.

Question 5

How to disable a specific rule in eslint-plugin-jest?

Accepted Answer

In your ESLint config, set the rule to 'off'. For example, in a flat config: `rules: { 'jest/prefer-expect-assertions': 'off' }`. You can also customize shareable configs by extending and overriding rules.

Question 6

What's the difference between recommended and style configs?

Accepted Answer

The `recommended` config enforces error-prevention rules like `no-conditional-expect`, while `style` adds stylistic rules like `prefer-to-be` for cleaner assertions. Use both for comprehensive linting.

Enforcing practices

What is Enforcing practices?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions