Read the Oxlint migration guide
Migration instructions for moving an existing Oxlint project or testing Oxlint as a new baseline.
Standardize your Oxlint workflow with Ultracite
Ultracite keeps the Oxlint and Oxfmt stack your team already chose, then adds a reusable baseline for presets, editor defaults, and staged rollout so speed-first teams do not reinvent the setup in every repository.
What Ultracite adds for Oxlint teams
This route is for teams that already chose Oxlint and want a cleaner, more repeatable way to standardize that stack across projects.
Why Oxlint teams add Ultracite on top
Oxlint teams usually do not need to be convinced about speed anymore. What they need is a way to turn that provider choice into a repeatable team standard instead of a collection of one-off repo decisions.
Ultracite helps by giving the stack a documented baseline that can survive onboarding, repo creation, and editor differences.
How Ultracite standardizes the Oxlint workflow
The biggest win is not a new linter. It is a reusable setup story. Presets, editor defaults, and migration guidance stop living in tribal knowledge and start living in one place.
That matters most when multiple teams or repos are trying to adopt Oxlint without drifting into subtly different local conventions.
Where Oxlint still differs from Biome and ESLint
Oxlint is not a universal replacement for every team today. Biome is simpler if you want a single tool for linting and formatting, and ESLint still has the deepest plugin ecosystem.
Ultracite keeps those tradeoffs visible. It strengthens the Oxlint path, but it does not pretend the differences from Biome and ESLint disappear.
What Ultracite adds to your Oxlint and Oxfmt setup
Oxlint and Oxfmt stay separate, but Ultracite moves the shared defaults into presets so your speed-first stack is easier to keep aligned across repos without rebuilding the same config by hand.
{ "$schema": "./node_modules/oxlint/configuration_schema.json", "extends": [ "./node_modules/ultracite/config/oxlint/core/.oxlintrc.json", "./node_modules/ultracite/config/oxlint/react/.oxlintrc.json", "./node_modules/ultracite/config/oxlint/next/.oxlintrc.json" ]}Why Oxlint teams add Ultracite on top
Oxlint teams reach for Ultracite when they already believe in the speed-first stack and want a cleaner way to standardize presets, editor defaults, and rollout decisions across multiple repos.
50-100x faster
Lint your entire codebase in milliseconds. No more waiting for slow linting processes.
15 plugin equivalents
Built-in support for React, TypeScript, Next.js, Vue, Jest, Vitest, JSDoc, and more without extra deps.
Bug-focused rules
Prioritizes catching real bugs over stylistic issues. High signal-to-noise ratio.
Oxc ecosystem
Part of the larger Oxc project with parser, resolver, transformer, and minifier built for speed.
Category-based config
Rules organized into correctness, suspicious, pedantic, performance, restriction, and style categories.
Drop-in ready
Works alongside your existing ESLint setup or as a complete replacement with Oxfmt for formatting.
Oxlint migration FAQ
These are the questions that come up when a team is seriously considering Oxlint for performance reasons and wants an honest view of the tradeoffs.
Related Oxlint resources
Use the migration guide when you are rolling the stack out and the provider docs when you need a deeper reference on presets, formatter defaults, and editor setup.
Review the Oxlint provider docs
Provider reference docs covering rule categories, formatter defaults, and extension setup for Oxlint and Oxfmt.
Trusted by top companies
And used by thousands of open source projects.
What the community is saying
Here's what some of the most innovative and forward-thinking developers in the React ecosystem have to say about Ultracite.