Can I keep custom ESLint plugins with Ultracite?

No. Ultracite packages a strong default, but you can still layer in project-specific plugins and overrides when your stack needs them.

Why does Ultracite still generate three config files for ESLint?

Yes. That separation is deliberate. ESLint continues handling code quality, Prettier handles formatting, and Stylelint covers CSS so you keep the mature ecosystem behavior many teams already trust.

When is ESLint the better choice than Biome or Oxlint?

Choose ESLint when ecosystem compatibility matters more than raw speed. If you need the broadest set of integrations and framework-aware linting, ESLint is still the safer default.

Will I still get type-aware linting?

Yes. Ultracite's ESLint presets preserve type-aware linting and the deeper analysis many TypeScript-heavy teams rely on for correctness.

Should I switch away from ESLint just to go faster?

If your team is mainly trying to reduce waiting time, Oxlint is worth evaluating. If your pain is configuration sprawl rather than execution speed, keeping ESLint through Ultracite is usually the lower-risk move.

Ultracite

Read the docs

Stay on ESLint, Prettier, and Stylelint with less setup burden

Ultracite preserves the mature ESLint, Prettier, and Stylelint workflow while packaging the defaults, plugin choices, and editor expectations that usually get copied from repo to repo by hand.

When the ESLint ecosystem is still the right call

This route is for teams that want stronger defaults and less maintenance while staying inside the most established linting ecosystem.

Choose ESLint for broader ecosystem coverage

ESLint keeps winning when your team needs plugin breadth, mature framework integrations, or rule coverage that has grown with the wider JavaScript and TypeScript ecosystem.

For larger organizations or unusual stacks, that compatibility can matter more than shaving every last second off the lint run.

How Ultracite reduces ESLint setup churn

Ultracite improves the ESLint path by packaging the repetitive defaults: plugin selection, formatter alignment, Stylelint wiring, and editor behavior.

You still get the flexibility of the classic stack, but you spend less time rebuilding the same conventions in every repo.

When staying on ESLint is the safer choice

Some teams should absolutely stay on ESLint. If your workflow depends on specialized plugins, highly customized framework rules, or deep type-aware coverage, the migration risk of switching away is rarely worth it.

Ultracite is useful here because it reduces maintenance overhead without forcing that trade.

What changes in your ESLint, Prettier, and Stylelint setup

Ultracite keeps the three-tool model intact. You still get dedicated config for ESLint, Prettier, and Stylelint, but the presets absorb the repetitive setup work that usually sprawls across projects.

import { defineConfig } from "eslint/config";import core from "ultracite/eslint/core";import react from "ultracite/eslint/react";import next from "ultracite/eslint/next";export default defineConfig([  {    extends: [      core,      react,      next    ],  },]);

Why teams keep the ESLint ecosystem and still use Ultracite

ESLint remains the safest choice when your team depends on plugin coverage, type-aware rules, or framework-specific linting behavior that has grown up around the wider JavaScript ecosystem.

Battle-tested

Used by millions of developers worldwide. The largest ecosystem of plugins and configurations available.

20+ plugins included

React, TypeScript, JSX A11y, Import, Promise, Node, Next.js, Unicorn, SonarJS, and more preconfigured.

Three tools in one

ESLint handles code quality, Prettier ensures consistent formatting, and Stylelint keeps your CSS clean.

Framework-aware

First-class support for React, Next.js, Vue, Svelte, and more with framework-specific rules.

Type-aware linting

Deep TypeScript integration with type-aware rules that catch bugs static analysis alone can't find.

Maximum coverage

Hundreds of rules covering accessibility, security, performance, and best practices out of the box.

ESLint migration FAQ

These are the usual questions from teams that want less config churn but do not want to abandon the mature ESLint ecosystem.

Related ESLint resources

Use the migration guide when you are updating an existing stack and the provider docs when you need a deeper reference on plugins, formatter defaults, and editor setup.