Question 1

How do I make XO use spaces instead of tabs?

Accepted Answer

Use the --space flag when running XO or set space: true in your xo.config.js file. You can specify the number of spaces, like space: 4, for custom indentation without messing with ESLint rule configs.

Question 2

XO or ESLint: which is better for a new project?

Accepted Answer

Choose XO if you want opinionated defaults with minimal setup, as it bundles useful plugins and handles TypeScript automatically. Use ESLint directly if you need fine-grained control over every rule or have highly specific custom requirements.

Question 3

Can XO lint Vue.js components?

Accepted Answer

Yes, but it requires manual setup: install eslint-plugin-vue and spread its recommended config in your xo.config.js. This adds Vue linting rules, though it's not zero-config like core XO features.

Question 4

How do I ignore a specific folder in XO?

Accepted Answer

Add the folder to the ignores array in your xo.config.js, or use the --ignore flag in the CLI. For example, ignores: ['dist/'] to exclude build directories, and you can negate defaults with patterns like '!vendor/**'.

Question 5

Does XO work with Prettier for code formatting?

Accepted Answer

Yes, set the prettier option to true in config to format with Prettier, or 'compat' to disable conflicting rules and use Prettier separately. XO merges its defaults with your Prettier config, but contradicting options will throw an error.

Question 6

What's the difference between XO and Standard JS?

Accepted Answer

XO is more pragmatic and configurable, with sensible defaults that can be overridden, while Standard enforces a fixed style without configuration. XO also includes more plugins like unicorn and better TypeScript support out of the box.

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