Cam McHenry
@camchenry.com
dad | software engineer @github.com | core team member of oxc.rs | ✝️
camchenry.com
camchenry.com
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.
November 8, 2025 at 2:04 AM
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.
On the Kibana repository, oxlint 1.24 is 11% faster than v1.23, and up to 26% faster than v1.22 and below!
October 22, 2025 at 4:59 PM
On the Kibana repository, oxlint 1.24 is 11% faster than v1.23, and up to 26% faster than v1.22 and below!
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!
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!
October 22, 2025 at 4:56 PM
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!
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!
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.
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.
October 13, 2025 at 6:11 PM
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.
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.
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.
The result: linting is around 15% faster in practice.
August 18, 2025 at 2:51 AM
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.
The result: linting is around 15% faster in practice.
This allows these errors to be displayed similarly to how they are rendered in the oxlint CLI, which is very helpful for more in-depth diagnostics!
April 7, 2025 at 4:44 PM
This allows these errors to be displayed similarly to how they are rendered in the oxlint CLI, which is very helpful for more in-depth diagnostics!
Also added within the last few weeks, lint errors which point to multiple areas in the code are now labeled and shown correctly in VS Code. Previously, this would cause these errors to not be shown sometimes.
April 7, 2025 at 4:38 PM
Also added within the last few weeks, lint errors which point to multiple areas in the code are now labeled and shown correctly in VS Code. Previously, this would cause these errors to not be shown sometimes.
In the latest version of the `oxc` VS Code extension (0.16.5), lint fixes now use the provided fix message whenever possible, making it much more clear what the fix will do.
Previously, this just appeared as "Fix XYZ problem".
Previously, this just appeared as "Fix XYZ problem".
April 7, 2025 at 4:35 PM
In the latest version of the `oxc` VS Code extension (0.16.5), lint fixes now use the provided fix message whenever possible, making it much more clear what the fix will do.
Previously, this just appeared as "Fix XYZ problem".
Previously, this just appeared as "Fix XYZ problem".
Society if engineers were banned from playing Factorio:
November 12, 2024 at 7:40 PM
Society if engineers were banned from playing Factorio:
and in this new country, we shall have 13 different types for text
and text shall be known as strings
and we shall call lists of things "vectors." what's the difference? nobody knows.
and text shall be known as strings
and we shall call lists of things "vectors." what's the difference? nobody knows.
November 5, 2024 at 7:44 PM
and in this new country, we shall have 13 different types for text
and text shall be known as strings
and we shall call lists of things "vectors." what's the difference? nobody knows.
and text shall be known as strings
and we shall call lists of things "vectors." what's the difference? nobody knows.
obligatory puppy coworker pics:
October 31, 2024 at 4:08 PM
obligatory puppy coworker pics: