How you can Migrate from ESLint to Oxlint

by DS | Dec 3, 2025 | Etcetera | 0 comments

ESLint has been the standard for over a decade. It’s mature, battle-tested, and intensely customizable with a huge ecosystem of plugins and regulations.

It has become an an important software in large JavaScript and TypeScript duties. It catches errors and keeps your code consistent.

On the other hand as duties increase, ESLint can become slow and resource-heavy. What will have to be a handy guide a rough feedback loop frequently turns proper right into a bottleneck, slowing developers and using up CI/CD costs.

Enter Oxlint.

Table of Contents

What’s Oxlint?

Oxlint is a high-performance linter for JavaScript and TypeScript built utterly in Rust.

Its serve as is to create a simple toolchain that is fast, lightweight, and easy to use. With 0 setup required, Oxlint comes in a position to catch no longer bizarre errors and redundant code right kind out of the sphere.

Listed below are one of the vital key choices that make Oxlint a ravishing variety to ESLint:

Serve as	ESLint	Oxlint
Core Technology	Node.js	Rust
Execution Sort	Necessarily Single-Threaded	Parallelized, Multi-Core Scaling
Configuration	Requires particular configuration for capacity	0 configuration required

Now, how do you in fact switch from ESLint to Oxlint?

Fortunately, the process is lovely easy.

We’ll walk all over the stairs for setting it up, converting ESLint in your workflow, and making sure your team of workers gets the capability boost without losing the guardrails you rely on.

Migrating Provide Undertaking

The ones steps assume that you already have ESLint prepare in your undertaking and that it has an ESLint flat config report.

To get started, you’ll run:

npx @oxlint/migrate eslint.config.mjs

After running the migration command, you will have to see a brand spanking new record known as .oxlintrc.json in your undertaking checklist. This record contains the migrated configuration from your ESLint flat config record.

Now, you’ll run the oxlint CLI in your undertaking.

npx oxlint@latest

This will sometimes lint your undertaking the use of the principles defined throughout the .oxlintrc.json record. In this case, it seems like there’s something that will have to be mounted in one of the crucial undertaking data.

On the other hand, if you need arrange it as a dev dependency, you’ll run:

npm arrange --save-dev oxlint

Then, you’ll add a script on your bundle deal.json:

{
    ...
    "scripts": {
        "lint": "oxlint"
        ...
    }
}

Now, you’ll simply run the linter with:

npm run lint

Coping with Unsupported Regulations

Oxlint is helping relatively a large number of regulations which include the core ESLint laws themselves, typescript, and eslint-plugin-react.

Then again, there can be some regulations that aren’t however implemented, as confirmed beneath:

Whilst you bump into any unsupported regulations everywhere the migration process, like those confirmed above, and you still wish to retain the ones regulations in your undertaking, you’ll use eslint-plugin-oxlint as an alternative.

This allows you to continue the use of your provide ESLint regulations while taking advantage of Oxlint’s capability benefits.

To place within the plugin, you’ll run:

npm arrange --save-dev eslint-plugin-oxlint

After it’s been installed, you’ll add the principles from the previously generated record on your ESLint config record:

import oxlint from 'eslint-plugin-oxlint';

export default [
  ..., // Load other ESLint plugins.
  ...oxlint.buildFromOxlintConfigFile('./.oxlintrc.json'), // Load rules from Oxlint config file.
];

Next, substitute the lint script in your bundle deal.json to include running each and every oxlint and eslint:

{
  "scripts": {
    "lint": "npx oxlint && npx eslint"
  }
}

This way, you’ll however use ESLint for the unsupported regulations while taking advantage of Oxlint’s pace for the rest of the code linting needs.

Wrapping Up

Switching from ESLint to Oxlint isn’t with regards to changing equipment. It’s about optimizing your workflow and lowering the pain of slow linting.

ESLint is still tough with its rich ecosystem, then again Oxlint takes a contemporary approach by means of that specialize in capability and straightforwardness right kind out of the sphere.

Built in Rust and designed with a zero-config setup, Oxlint offers you lightning-fast linting that scales even in large duties.

I’d recommend giving it a take a look at in a couple of of your small to medium-sized duties. It’s essential to be shocked at how so much quicker and smoother your building process feels.

The submit How you can Migrate from ESLint to Oxlint appeared first on Hongkiat.

WordPress Website Development

Supply: https://www.hongkiat.com/blog/eslint-to-oxlint-migration-guide/

[ continue ]