refactor(linter): migrate from eslint to oxlint #152
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Coverage Report
File Coverage |
soyuka
approved these changes
Jun 13, 2025
- expect-expect - no-conditional-expect - no-conditional-in-test - no-standalone-expect
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Oxlint — A Quick Intro
Oxlint is a next-generation JavaScript / TypeScript linter written in Rust.
Its 1.0 “stable” release (10 Jun 2025) makes it a production-ready, drop-in alternative to ESLint with dramatic performance gains and native TypeScript parsing.
Key Advantages over ESLint
Brutal performance – Rust + SIMD + multithreading make Oxlint ~50-100 × faster than ESLint in real-world benches.
Tiny memory footprint – avoids Node-JS heap spikes; runs comfortably under ~150 MB even on large codebases.
Better DX – colourful code-frames, inline autofix hints, and clearer wording cut review time.
TypeScript-first – parses TS natively; no separate
@typescript-eslintstack required.Drop-in coverage – 500 + rules today, plus an
eslint-plugin-oxlintshim to smooth migration.Single binary, tiny
node_modules– the whole lint stack collapses from hundreds of JS packages to one ~5 MB binary.Scales with core-count – automatic parallelism on CI runners; ESLint is single-threaded.
What this PR does
tsconfigoptions (erasableSyntaxOnly, etc.) and fix resulting type errors.npm run lint) to calloxlint.Changelog
Bug Fixes
Miscellaneous Chores
blocked by #151