con un clic
oxlint
Use when configuring .oxlintrc.json or lint-related CI
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Use when configuring .oxlintrc.json or lint-related CI
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Bun is an all-in-one JavaScript/TypeScript toolkit that ships as a single binary. It includes a runtime (drop-in Node.js replacement), package manager, test runner, and bundler.
WXT web extension framework — entrypoints, manifest generation, content scripts/UI, storage, messaging, modules, CLI, browser targets, publishing. Use when building, debugging, configuring, migrating, or publishing browser/web extensions with WXT.
Read this skill before serving as orchestrator
Read before writing user-facing docs — READMEs, tutorials, how-to guides, reference docs, or any prose for human readers. Use when creating or substantially editing docs aimed at users rather than agent-facing files like AGENTS.md.
Delegate work to configured subagents with single-agent, chain, parallel, async, forked-context, and intercom-coordinated workflows. Use only agents discovered from user or project Markdown agent files.
Use this skill when working directly with any of the following - Cloudflare Workers, Durable Objects, R2, D1, SecretsStore, Queues, Hyperdrive, EmailRouting, EmailSending, Containers; Drizzle; Axiom
| name | oxlint |
| description | Use when configuring .oxlintrc.json or lint-related CI |
Oxlint (/oʊ-ɛks-lɪnt/) is a high-performance linter for JavaScript and TypeScript built on the Oxc compiler stack.
Oxlint is built for large repositories and CI environments. Its architecture removes structural bottlenecks that limit performance in ESLint.
Our benchmarks show Oxlint is 50 to 100 times faster than ESLint.
Oxlint is useful out of the box. By default, it prioritizes high-signal correctness checks. These checks surface code that is incorrect, unsafe, or useless, so teams can adopt Oxlint without excessive noise.
Additional rules can be enabled incrementally as requirements evolve.
To make migration simple, Oxlint includes more than 756 rules, with coverage across the linter plugins most teams already use, including:
This breadth makes migration straightforward without sacrificing rule coverage. And tooling has been built to migrate your entire linter config for you.
Oxlint leverages the native Go port of the TypeScript compiler (tsgo aka TypeScript 7), providing full TypeScript compatibility and the same type system behavior you expect from TypeScript itself.
This enables mission critical checks that require types, such as detecting floating promises.
In contrast, Biome’s approach is to implement its own type inference instead of relying on the TypeScript compiler, and they note coverage is still improving.
See: Type-aware linting
Oxlint supports multi-file analysis as a first-class capability.
When enabled, Oxlint builds a project-wide module graph and shares parsing and resolution across rules. This improves checks that depend on cross-file imports and helps avoid the performance cliff often seen with rules like import/no-cycle in ESLint.
See: Multi-file analysis
Oxlint diagnostics are designed to be both human-readable and machine-actionable.
In addition to clear messages, diagnostics include structured information such as precise spans, contextual data, and links to relevant documentation. This helps AI to understand issues and apply fixes reliably.
Oxlint is built for workflows where failures are not acceptable.
Crashes are treated as top priority bugs. Performance regressions are treated as bugs.
Stability and throughput are always prioritized, especially for CI and large monorepos.
The recommended setup is to install Oxlint as a dev dependency and add scripts.
pnpm add -D oxlint
Add scripts to package.json:
{
"scripts": {
"lint": "oxlint",
"lint:fix": "oxlint --fix"
}
}
Next steps:
Tip: If you're migrating from ESLint, see the "Migrate from ESLint" page for detailed guidance.
Choose the approach that fits your repository:
@oxlint/migrate to migrate your existing ESLint config.eslint-plugin-oxlint to disable overlapping ESLint rules while running both.@oxlint/migrate for this approach as well.Oxlint supports:
.js, .mjs, .cjs, .ts, .mts, .cts).jsx, .tsx).vue, .svelte, .astro) by linting only their <script> blocksSee the compatibility matrix for detailed framework support.
Oxlint is used in production by popular projects such as: