Question 1

How do I override rules in eslint-config-standard?

Accepted Answer

You can extend the configuration in your eslint.config.js file and add custom rules. For example, after requiring eslint-config-standard, include an object with your overrides, as shown in the README's usage snippet.

Question 2

eslint-config-standard vs standard: which should I use?

Accepted Answer

Use the standard CLI for a simpler, zero-configuration experience. Choose eslint-config-standard if you need to integrate Standard Style into an existing ESLint setup or require custom rule modifications, as it offers more flexibility but requires ESLint knowledge.

Question 3

Does eslint-config-standard work with TypeScript or React?

Accepted Answer

No, it's designed for vanilla JavaScript. For TypeScript or React, you'll need additional ESLint configs or plugins, and you might have to override rules to handle JSX or TypeScript syntax, which isn't covered out of the box.

Question 4

How to integrate eslint-config-standard into VS Code?

Accepted Answer

Install the ESLint extension in VS Code and ensure your project's eslint.config.js includes eslint-config-standard. The extension will automatically apply the rules, but you may need to configure it to use the flat config format.

Question 5

What are the main rules enforced by eslint-config-standard?

Accepted Answer

It enforces JavaScript Standard Style rules, such as no semicolons, 2-space indentation, and preferring single quotes. For a full list, refer to the Standard Style documentation linked in the README.

Question 6

Is eslint-config-standard compatible with Prettier?

Accepted Answer

It can conflict with Prettier since both handle formatting. You might need to disable overlapping rules or use a tool like eslint-config-prettier to avoid clashes, which adds complexity to your setup.

Standard

What is Standard?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions