29.01.2026 18:43
👍 1
🔁 0
💬 0
📌 0
yep, but to use oxlint + type aware rules, you’ve already got two binaries. you can drop the third (tsgolint), by using the built in —type-check
copilot seems to just be wrong here.
We shipped custom JS plugin support a few months ago. Any rules that have not been ported to rust can be used via custom plugins.
Using custom plugins should mitigate all four of the problems mentioned by copilot in the PR description.
let us know how you get on!
what was it? could we improve our docs?
let me raise it, its still pre-alpha so some options may not be implemented yet.
config file docs >>
github.com/oxc-project/...
On my laptop, oxlint 1.24 is 3% faster than 1.23 on the `vscode` repository, with even larger improvements for very large codebases.
That means if you haven't updated to one of the latest versions in a few weeks, your linting step could be >10% slower than it should be!
check out the awesome work Cam has been doing!
definitely! once i’ve polished it off, i will upstream
To add, the perf difference is when running oxlint with type aware rules against github.com/toeverything/A…
with: `oxlint --type-aware -A all -W no-floating-promises --silent ./vitest.config.ts`
These perf improvements werre possible via changes to tsgo.
we're making typescript-go faster for tsgolint!
optimizing the tsconfig file registry has yielded a 52x perf improvement when benchmarking against affine and we've got more on the way:
154.61s user 21.70s system 812% cpu 21.711 total
0.71s user 0.84s system 369% cpu 0.417 total
