Conversation
✅ Deploy Preview for oxc-project ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
d5dfd8c to
1582e72
Compare
|
I've pushed a commit with a very rough draft. Lots of gaps, and it's not slick writing, lots of repetition. Purpose is to communicate the broad strokes of what I think the thrust should be. In short: We need to set expectations about performance - this release is about API coverage and JS plugins actually usable in the real world, not stellar performance. That said, we've not done a lot of benchmarking yet. Once we do, if it performs better/worse than expected, we can tilt the narrative a bit. |
|
I think you can also speak to the benefits of being able to move over more fully. Even if some individual rules are run via JS Plugins and are slower than they would be in ESLint, more than 640 rules have been ported to Rust. So if you have a large project and the slowest rules in ESLint are because of the import plugin, you can switch to oxlint right now, use native Rust versions of those rules for a huge performance boost, and then maybe you lose a bit of perf on some other plugins that still run via JS, but that's probably fine. It depends on the specifics of your needs and your project, but:
So if you migrate right now, your setup will likely become >10x faster even with some JS-based rules dragging things down, and it'll only get faster as we continue to improve :) |
|
|
||
| ### What it can't do (yet) | ||
|
|
||
| - No language server support yet. Errors from JS plugins are reported from Oxlint's CLI, but not in IDEs. |
There was a problem hiding this comment.
| - No language server support yet. Errors from JS plugins are reported from Oxlint's CLI, but not in IDEs. |
so we do not forget :)
hypothetical release date: 2025-12-22