Question 1

How does XO compare to Standard JS?

Accepted Answer

XO is more pragmatic and configurable than Standard JS, which enforces a single, unchangeable style. XO offers opinionated defaults but allows customization, and it includes more built-in plugins and TypeScript support, as explained in the 'Why not Standard?' FAQ.

Question 2

How to set up XO with React?

Accepted Answer

Enable the react option in your xo.config.js or use the --react flag to automatically include eslint-plugin-react and related rules. For zero-config setup, you can also use eslint-config-xo-react, as detailed in the 'react' config section.

Question 3

Does XO work with TypeScript automatically?

Accepted Answer

Yes, XO lints TypeScript files by default with automatic tsconfig.json handling, so no extra configuration is needed. It uses eslint-config-xo-typescript under the hood, as described in the 'TypeScript' section.

Question 4

Can XO fix code issues on its own?

Accepted Answer

Yes, XO can automatically fix many common issues like formatting errors when you run it with the --fix flag. This saves time and ensures consistency across the codebase, as shown in the CLI options.

Question 5

What are XO's default code style rules?

Accepted Answer

XO defaults include tab indentation, semicolons, single quotes, trailing commas for multiline statements, and strict equality (===). These are designed for readability and can be overridden in config, as listed in the 'Default code style' section.

Question 6

How to integrate XO with Prettier?

Accepted Answer

Set the prettier option to true in config to format code with Prettier, or use 'compat' to disable conflicting rules. XO merges Prettier options with its defaults, and contradictions cause errors, as explained in the 'prettier' config section.

xo

What is xo?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions