Question 1

How do I disable a specific rule in Standard?

Accepted Answer

Use ESLint disable comments like // eslint-disable-line, as Standard runs on ESLint under the hood. For multiple lines, wrap code with /* eslint-disable */ and /* eslint-enable */ comments as shown in the README.

Question 2

Standard vs ESLint: which should I use?

Accepted Answer

Choose Standard for zero-config, opinionated consistency to save time on setup and debates. Use ESLint directly if you need fine-grained control over hundreds of rules or custom configurations for complex projects.

Question 3

Does Standard work with TypeScript?

Accepted Answer

Not directly; you must use the ts-standard variant for integrated support or configure Standard with @babel/eslint-parser and plugins, which adds overhead compared to plain JavaScript projects.

Question 4

How to ignore files or folders in Standard?

Accepted Answer

Add a standard.ignore array in package.json or rely on automatic ignores like node_modules/. The README also mentions using .gitignore patterns for additional exclusions.

Question 5

Can Standard fix all errors automatically?

Accepted Answer

No, standard --fix corrects most style issues, but logical errors like unhandled exceptions must be fixed manually. The README notes it outputs a message suggesting --fix for auto-fixable problems.

Question 6

What if I want to use semicolons with Standard?

Accepted Answer

Consider using semistandard, a fork that allows semicolons, or switch to eslint with eslint-config-standard. The README recommends sticking with Standard to avoid style debates.

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