migrate lint stack to Oxlint + Oxfmt#19179
Merged
ornicar merged 3 commits intolichess-org:masterfrom Jan 21, 2026
Merged
Conversation
ornicar
added a commit
that referenced
this pull request
Jan 22, 2026
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
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.
Why
Oxlint + Oxfmt are Rust-based replacement for ESLint + Prettier. They rely on multithreading and offer a significant performance gains, with no local cache needed. They also have support for multiple editors and IDEs via plugins/extensions, so migration for maintainer should also be a smooth process.
How
Migrate lint stact to Oxlint + Oxfmt while trying to retain previous scripts, code organization and ruleset, aiming at 1:1 conversion for now.
To prevent new warnings/errors to pop I had to disable few enabled by default rules, but it might be worth to revisit, and try to fix them in near future. There are definitely more rules which can be enabled to address some potential issues and code styling, the list of all supported ones can be found at https://oxc.rs/docs/guide/usage/linter/rules.html.
Additionally, I would recommend enabling import grouping and sorting (https://oxc.rs/docs/guide/usage/formatter/sorting.html) by the formatter.
Unfortunately, there is one rule which is not currently supported by the toolset, nor have an alternative, and it is
no-restricted-syntaxrule. Please let me know if this is a blocker for the migration - for now I have left the inline comments associated with that rule, where it was enabled manually. Already enablednoUncheckedSideEffectImports(https://www.typescriptlang.org/tsconfig/#noUncheckedSideEffectImports) TypeScript config option should prevent some issues, but definitely not all of them, which were previously covered by ESLint.Besides the migration, this changeset includes few formatting changes and warning fixes:
Any feedback or suggestions are appreciated!
Preview