On the specifics: If you'd have time to try latest version, and let us know what missing APIs are blocking you, likely we can fix it swiftly. We want to support all users, not just the simple cases.

I think a lot of people don't customise their tools much, beyond pulling in plugins from NPM. This doesn't at all match how I work, but hey... I guess there's a reason I work in tooling.

We did say "almost" the entire API surface. Which missing methods are blocking you? `sourceCode.markVariableAsUsed` is the only ESLint v9 SourceCode method that we're missing to my knowledge.

Helped "a little bit" my arse! Your contribution to Oxlint is massive, and each part builds on every other part. Thank you.

Thanks for supporting Oxlint too!

We don't have a good solution for this - and nor do TS team from what I gleaned! (though my knowledge may be out of date on last point)

I'm afraid no current plans. We understand how useful it would be, but it'd be really hard. tsgo doesn't expose the required info, and even if it did, the perf would probably be terrible - way too much boundary crossing between JS and Go.

Can you share your benchmark code please?

Just to add that we added `eslint-plugin-react-hooks` to our conformance testing for Oxlint JS plugins today and 100% of the 5000 tests pass (including React Compiler rules).

"We build, so you don't have to" 😀

Big up to new #oxc contributor @arsh.sh, who showed up out of nowhere and is tearing through our issue list! He's just implemented support for all the comment-based APIs in Oxlint JS plugins. github.com/oxc-project/...

2 team members working on it now. It won't be too long!

Oxlint will soon have support for JS plugins, with an ESLint-compatible API. So at that point the rules which Oxlint doesn't support natively will be able to run as JS plugins.