Question 1

How to integrate eslint-plugin-only-warn with Husky and lint-staged?

Accepted Answer

Install the plugin, add it to your ESLint config, then set up Husky with a pre-commit hook that runs lint-staged with eslint --max-warnings=0 on staged files, as outlined in the README's Git integration section. This ensures no warnings are committed.

Question 2

Does eslint-plugin-only-warn work with ESLint flat config files?

Accepted Answer

Yes, the README provides examples for both flat config (eslint.config.js) and traditional .eslintrc formats, ensuring compatibility with ESLint's latest configuration system and older versions.

Question 3

eslint-plugin-only-warn vs setting all ESLint rules to warnings manually?

Accepted Answer

This plugin automates the process, saving time and ensuring consistency across all rules without manual updates. Manually setting each rule can be error-prone and tedious, especially in large codebases with many rules.

Question 4

Can I still have some rules as errors while using this plugin?

Accepted Answer

No, the plugin downgrades all errors to warnings uniformly. If you need specific rules to remain errors, you'd need to override them separately in ESLint config or consider not using the plugin for those cases.

Question 5

Is eslint-plugin-only-warn compatible with TypeScript and @typescript-eslint?

Accepted Answer

Yes, it works with any ESLint setup, including TypeScript projects, as it operates at the plugin level and doesn't interfere with rule definitions from @typescript-eslint or other extensions.

Question 6

What happens to fatal ESLint errors with this plugin?

Accepted Answer

Fatal errors, such as configuration issues, are still reported as errors and not downgraded, ensuring critical problems that prevent ESLint from running are caught immediately.

Only-Warn

Overview

Use Cases

Not Ideal For

Pros & Cons

Pros

Related Projects

Found a gem we're missing?

Cons

Frequently Asked Questions