Advertisement · 728 × 90

Posts by

We're hoping that once the Rustified React Compiler drops (React team are working on it now) we can implement react-hooks rules on Rust side. And, yes, Oxlint needs a cache! Before JS plugins and type-aware rules, Oxlint was so fast, caching was pointless. But the game has changed now.

1 month ago 2 0 0 0

Are you using latest Oxlint version? We removed the warning about potential API changes a few versions back. I'd recommend upgrading - more recent versions have some significant perf improvements.

1 month ago 0 1 1 0
Oxlint JS Plugins Milestone 3 · Issue #19918 · oxc-project/oxc Milestone 2 (#14826) is now complete. Pretty much the whole of ESLint's plugin API surface is supported by Oxlint. Conformance tests show very high pass rate (99.5%+ on popular plugins). Next miles...

The day is coming! Can't promise when exactly, but coming... github.com/oxc-project/...

1 month ago 1 1 1 0

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.

1 month ago 0 0 0 0

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.

1 month ago 0 0 2 0

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.

1 month ago 0 0 1 0

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

1 month ago 4 0 0 0

Thanks for supporting Oxlint too!

1 month ago 1 0 0 0

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)

2 months ago 2 0 0 0

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.

2 months ago 1 0 1 0
Advertisement

Can you share your benchmark code please?

2 months ago 4 0 2 0

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).

2 months ago 4 0 1 0

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

5 months ago 4 0 0 0
feat(linter/plugins): comment-related APIs by lilnasy · Pull Request #14715 · oxc-project/oxc Part of #14564. Implement the remaining SourceCode APIs related to comments (getCommentsBefore, getCommentsAfter, getCommentsInside, commentsExistBetween).

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/...

6 months ago 34 4 0 1

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

6 months ago 1 0 0 0

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.

6 months ago 1 0 0 0