tools: upgrade oxlint and make it do more eslint stuff #2931
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.
With type-aware linting and preliminary plugin support, oxlint is closing in on being a full eslint replacement. It's not there yet (I don't think it supports all our plugins yet) but it's almost there. This PR just tweaks the config and npm run scripts to cover more of the stuff eslint catches. This is primarily for speed in local dev. When we want to switch for real we'll want to validate that oxlint is really covering all the stuff we care about that eslint is doing for us by looking at
npx eslint --print-config .eslintrc.jsandnpx oxlint --print-config.https://oxc.rs/blog/2025-08-17-oxlint-type-aware.html
https://oxc.rs/blog/2025-10-09-oxlint-js-plugins.html