Question 1

How to override rules in eslint-config-auto?

Accepted Answer

You can add custom rules in your .eslintrc file under the 'rules' key to override defaults. Since it's a base config, extensions work normally, but be aware that automatic plugin detection might affect rule availability based on dependencies.

Question 2

eslint-config-auto vs eslint-config-airbnb: which should I use?

Accepted Answer

eslint-config-auto builds on eslint-config-airbnb by automatically adding plugins for dependencies and supporting multiple languages. Choose auto if you want adaptive setup; use airbnb directly for a static styleguide without extra plugins.

Question 3

Does eslint-config-auto work with Next.js?

Accepted Answer

It should work if Next.js dependencies like React are detected, but specific Next.js linting rules aren't mentioned. You might need custom configs for framework-specific optimizations, as auto focuses on general JavaScript and library support.

Question 4

Can I use eslint-config-auto in a project without package.json?

Accepted Answer

No, it relies on analyzing package.json for dependencies to select plugins, so projects without it won't benefit from automatic configuration. You'd need a manual ESLint setup in such cases.

Question 5

What testing frameworks does eslint-config-auto support?

Accepted Answer

It supports Jest, Mocha, Cypress, Ava, and others, automatically loading plugins based on devDependencies, as listed in the Test Libraries section, covering most common testing tools.

Question 6

How to disable Babel support in eslint-config-auto?

Accepted Answer

Babel support is auto-detected from devDependencies or enabled via settings in .eslintrc. To disable it, ensure Babel isn't in dependencies and avoid setting 'babel: true' in settings, though this might limit linting for Babel-transpiled code.

Auto

What is Auto?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions