Okay here's my bad idea github.com/camchenry/ox...

Cam McHenry@camchenry.com · 2mo ago

Against my better judgment, I have started a side project that is probably impossible to achieve practically. I'm gonna try anyway. Hopefully I will learn a lot 😅

Against my better judgment, I have started a side project that is probably impossible to achieve practically. I'm gonna try anyway. Hopefully I will learn a lot 😅

Speeding up the JS ecosystem OXC edition 🚀 We made both oxfmt and oxlint 50% faster on projects with >50k directories. marvinh.dev/blog/speedin...

Speeding up the JavaScript ecosystem - oxlint and oxfmt

Future versions of oxlint and oxfmt will be ~50% faster on projecs with many (>=20k) directories.

marvinh.dev

we recently added rule timing support to oxlint to help triage performance issues. try running with `--debug=timings` to see the slowest built-in rules. support for type-aware/JS plugins will be supported in the future too.

oxlint now supports 100%* of the eslint-plugin-jsx-a11y rules! final rules will be in the next release. github.com/oxc-project/...

☂️ eslint-plugin-jsx-a11y · Issue #1141 · oxc-project/oxc

WarningThis comment is maintained by CI. Do not edit this comment directly. To update comment template, see https://github.com/oxc-project/oxc/tree/main/tasks/lint_rules This is the tracking issue ...

github.com

We are working on bulk suppressions support in oxlint! Next release will have CLI support and we are working on LSP support now.

I have now replaced ESLint with Oxlint in the DebtBook Rails/React codebase 🫡 ESLint ran in 20s with full cache, 230s without cache. And somewhere in between very randomly depending on the changes made. Oxlint - with type-aware, a JS Plugin, and more than 250 rules - runs in around 8 seconds :)

Excited to see this! I want to make it work with oxlint as soon as possible 😀

Joe Savona@en-js.bsky.social · 4mo ago

The React Compiler rust port is now up as an in-progress PR at github.com/facebook/rea... - more to come as we test and polish.

Really interesting research from auvred on type-aware linting: github.com/auvred/hybri... This is the next frontier for developer tooling: cross-language interoperability and finding the right tradeoffs to make for extensibility/performance.

GitHub - auvred/hybrid-type-aware-linting-performance: Performance evaluation of different approaches for bridging tsgo with JS

Performance evaluation of different approaches for bridging tsgo with JS - auvred/hybrid-type-aware-linting-performance

github.com

Thank you @andrewbran.ch for upstreaming some perf optimization from tsgolint! github.com/microsoft/ty... I guess this counts as my first typescript-go contribution? 😅

Add per-directory module resolution cache by andrewbranch · Pull Request #3070 · microsoft/typescript-go

This upstreams oxc-project/tsgolint#764 from @camchenry. Thanks for the work there! This is a simpler than what we used to have, and avoids the lock contention that made caching worse than not cach...

github.com

Fun story from today. I'm currently trying to get `--strict` on by default in TypeScript 6.0. Our test suite has many tests which are written with `--strict false`, so I am updating them by adding a special comment our test suite recognizes for options // @strict: false However...

Try it out!

VoidZero@voidzero.dev · 8mo ago

Announcing Oxlint Type-Aware Linting Alpha 🎁 Just a few months after our technical preview, type-aware linting reaches the alpha milestone! ✨ Type-aware rules can now be configured 🙈 Inline comments to disable rules work for type-aware rules too ✔ Auto fixes for type-aware rules are now available

Announcing Oxfmt: Oxc Formatter Alpha oxc.rs/blog/2025-1...

Oxfmt: Oxc Formatter Alpha

A collection of high-performance JavaScript tools written in Rust

oxc.rs

It took a little while, but I feel like using `go tool pprof` is starting to grow on me.

This has been in the works for a few months now! Excited for more people to try this out when it supports config options. A special thanks to the @typescript-eslint.io team who have set the standard for typed lint rules here. Much of this work is based on what has come before and on their rules.

Boshen@boshen.github.io · 9mo ago

Thank you @camchenry.com for the long development of configuring type-aware rules! tsgolint alpha soon! github.com/oxc-project/...

Finally had time to put more effort into implementing oxlint<->tsgolint configuration for rules. Very soon, you'll be able to configure type-aware rules like any other rules. Should be as easy as just upgrading to the latest versions once it is available.

So I started working on it in the evenings when I had time, and last week while I was off work for a week (recovering from eye surgery), in between naps I worked through most of the rule updates. So now almost all of them have documentation for their config options :) github.com/oxc-project/...

linter: various rules are missing `options` documentation on the Rules pages of the website · Issue #14743 · oxc-project/oxc

I think this was covered slightly by #6050, but may have been missed as being within scope of the problem. no-unused-vars, for example, has various options available. But the page for the rule make...

github.com

I had been exploring ESLint alternatives and was bothered by the lack of consistent documentation for rule configs in oxlint. So I opened an issue about it and talked with the maintainers about the right way to solve it, and found out there was a system for auto-generating documentation with types.

linter: various rules are missing `options` documentation on the Rules pages of the website · Issue #14743 · oxc-project/oxc

I think this was covered slightly by #6050, but may have been missed as being within scope of the problem. no-unused-vars, for example, has various options available. But the page for the rule make...

github.com

I love that this actually works. *Oh yeah, is your list actually UNordered? Prove it.*

Tab Atkins-Bittner@tabatkins.com · 9mo ago

Add reading-flow, done.

use no memo hear no memo speak no memo

I am looking for a full-time job. Being independent in open source for 3.5+ years has been wonderful. I've gotten done most of the high-level goals I wanted to, and miss having people & structure around me. If you know of a role for a staff-level TypeScript+web developer, let me know! 🙂

Vite and Vitest imply the existence of Viter

Does anyone have experience with tools for benchmarking on every PR for Go projects? I'm looking to get a rough estimate of perf regressions/improvements in each PR for github.com/oxc-project/.... Looking into building something custom with `go tool pprof` currently.

GitHub - oxc-project/tsgolint: Type aware linting for oxlint

Type aware linting for oxlint. Contribute to oxc-project/tsgolint development by creating an account on GitHub.

github.com

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!

Cam McHenry@camchenry.com · 10mo ago

Oxlint 1.23.0 just got released, which includes the latest in some of the performance optimization work I've been doing. Running on the vscode repository on my M1 laptop, 1.23.0 is ~7-9% faster than previous versions of oxlint with no changes other than just bumping the dependency.

Making something 1% faster 20 times > making something 20% faster once But that doesn't stop me from trying to get that juicy big one 😅

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

Oxlint 1.23.0 just got released, which includes the latest in some of the performance optimization work I've been doing. Running on the vscode repository on my M1 laptop, 1.23.0 is ~7-9% faster than previous versions of oxlint with no changes other than just bumping the dependency.

Just finished writing up an auto-fix for this in Oxlint, in case this was a blocker for anyone: github.com/oxc-project/...

feat(linter): add fix for `preserve-caught-error` by camchenry · Pull Request #14104 · oxc-project/oxc

Ported over the tests from typescript-eslint. I also improved the diagnostic messages that were pre-existing. I believe the fixer now supports all of the same cases that typescript-eslint does, but...

github.com

Seb ⚛️ ThisWeekInReact.com@sebastienlorber.com · 11mo ago

I like this new lint rule 👏 Don't rethrow JS errors without a cause!

I'm finally starting to pick up Go and try to formally learn it. It's got a lot of wild features! First language I've used in quite a while that natively supports complex numbers, seems like an interesting choice. The swapped type declaration order is gonna take a while to get used to.

First of these optimizations rolled out in v1.15.0 with a reduced scope. Next version of oxlint will be even faster: github.com/oxc-project/... On my laptop: ~15% faster on `oven-sh/bun`, ~9% faster on `microsoft/vscode`, ~11% faster on `posthog/posthog`, and ~8% faster on `elastic/kibana`

perf(linter): detect node types from `let..else` statements by camchenry · Pull Request #13690 · oxc-project/oxc

part of linter: dynamically skip running rules that do not have the relevant node types #12223 Adds basic detection for syntax like let AstKind::Something(...) = node.kind() else { return }; in li...

github.com

Cam McHenry@camchenry.com · 12mo ago

Trying some new oxlint optimizations. This PR has gone over several iterations in the last few months and the core idea is simple: don't run rules for files if they don't apply (using an AST node bitset lookup). The result: linting is around 15% faster in practice.