migrate-oxlint

Migrate ESLint configurations to Oxlint and generate a compatible Oxlint setup.

22.3k|1.2k|Updated Feb 9, 2023
One-click install
npx skills add https://github.com/oxc-project/oxc --skill migrate-oxlint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-oxlint
Source: https://github.com/oxc-project/oxc/tree/main/.agents/skills/migrate-oxlint
Command: npx skills add https://github.com/oxc-project/oxc --skill migrate-oxlint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate ESLint configurations to Oxlint automatically, generating a compatible Oxlint setup to streamline lint modernization across JavaScript and TypeScript projects.

Core Features & Use Cases

  • Automated ESLint to Oxlint migration with configuration generation.
  • Plugin and rule mapping guidance to preserve behavior with Oxlint.
  • Use it in CI and development workflows to progressively adopt Oxlint without downtime.

Quick Start

Run the migration tool in your project root to generate the .oxlintrc.json

Frequently Asked Questions about migrate-oxlint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate an ESLint config to Oxlint?

You can migrate an ESLint config to Oxlint automatically by running the migration tool in your project root to generate a compatible .oxlintrc.json setup file. This translates existing plugins and rules for JavaScript and TypeScript projects.

What is the best way to convert ESLint rules to Oxlint for TypeScript?

The best way to convert ESLint rules to Oxlint for TypeScript is using an automated migration workflow that provides plugin mapping and rule translation guidance to preserve your original linting behavior.

Does Oxlint support all ESLint plugins during migration?

Oxlint migration provides guidance for plugin mapping and rule compatibility checks, but you should verify if specific ESLint plugins have direct Oxlint equivalents to ensure your JavaScript linting behavior is fully preserved.

Can I progressively adopt Oxlint in my CI workflow without downtime?

You can progressively adopt Oxlint in CI workflows without downtime by generating a compatible Oxlint setup and integrating it alongside your existing ESLint configuration during your modernization process.

What are the limitations of migrating ESLint to Oxlint?

Limitations of migrating ESLint to Oxlint include potential gaps in plugin mapping and rule translation, meaning some specific ESLint rules may lack direct Oxlint equivalents and require manual configuration adjustments.

Why does my ESLint to Oxlint migration need rule translation?

ESLint to Oxlint migration needs rule translation because Oxlint has different rule names and plugin structures, requiring compatibility checks to preserve your intended linting behavior across JavaScript and TypeScript projects.