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

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.

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? 😅

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!

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

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.

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

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.

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

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.

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!

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

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`

VoidZero x SquiggleConf: Win a ticket! VoidZero is a proud sponsor of this year's @squiggleconf.com on September 18th and 19th in Boston. We've got an extra ticket for the event and want to give it away to one of you so you can join us there! Learn in this thread how you can enter the raffle 👇

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.

Announcing Oxlint Type-Aware Preview oxc.rs/blog/2025-08...

Cool to see more tsgo-based linters! I think best practices here are not known yet, so it is great to see more teams innovating on this.

Great news for anyone linting large repositories! Hopefully this will be an easy performance win for teams using ESLint.

Just had a listen to this, it's well worth listening to catch up on the current state of JS linting, as Josh has lots of experience from working on ts-eslint. Lots of innovation happening in linting currently Overall, I think right now is a great time to learn more about linting, parsing, and ASTs.

First version is out! It's still pretty experimental, but we will keep improving performance and fixing bugs with each version. Most importantly though: you can use it now!

`oxlint --type-aware`. Mic drop. It's incomplete and have numerous problems, including a noticeable performance issue. BUT, you can finally see your floating promises quickly! Example PR: github.com/rolldown/rol... Problems: t.co/K7ZVnPjOPL

It's been great to work on prototyping this! I'm really excited by typescript-go and looking forward to getting this released as soon as we can. The future is fast ⚡️

I am permitted to host tsgolint in Oxc and explore type aware linting! I am super excited! We reduced the original scope of tsgolint to be a backend for oxlint, taking the best out of both worlds! github.com/oxc-project/...

Introducing tsl, an extension of tsc for type-aware linting! Want to speed up your ESLint time without losing the great type-aware rules from @typescript-eslint.io? Run `bunx tsl --migrate` to try it out! github.com/ArnaudBarre/...

This is the best explanation of ARIA that I've seen. There is so much practical advice in here as well!

We're thrilled to announce the first stable release of Oxlint - version 1.0! Our Rust-powered JavaScript/TypeScript linter delivers 50~100x faster performance than ESLint with 500+ rules and zero configuration required. Time to give it a try! voidzero.dev/posts/announ...

Today we are excited to announce Rolldown-Vite: a technical preview of the version of @vite.dev entirely powered by the Rust stack we built over the past year (Oxc + @rolldown.rs) voidzero.dev/posts/announ...

For the Oxlint 1.0 announcement, I'd like to show more real world performance numbers on large repos. If Oxlint has been satisfactory, would you be keen to send me the numbers Oxlint reports at the end? If you have never tried Oxlint but has a large repo: `npx oxlint@latest`.

I got involved with oxc because I just showed up, looked at the issues available and suggested solutions, and started making contributions. It was also nice to not have the pressure of being publicly assigned to it so I could take my time and learn as I went.

If you find an OSS issue that calls your attention, go for it. You don't need to ask permission to start working or have it assigned to you. If someone else sends a PR before you, that's great. You can use your knowledge of the issue to help review the PR, add tests, and validate the approach.

Happy to see Mercedes Benz adopting modern tooling such as @rolldown.rs and Oxc in their workflow, as well as going the extra mile and sharing their results! Up to 64% CI pipeline time reduction is impressive 👀 And more per improvements are yet to come 🤯 www.mercedes-benz.io/blog/2025-05...

Σ Experimental bundle analyzer in the last version of obuild.unjs.io @rolldown.rs is fast enough that we can build a package, generate types, then bundle it again, minify it with OXC, and then bundle again!! (for side-effect check) and still takes <50ms for a small lib!

A proof of concept to run ast-grep via OXC parser

On Oxlint JS plugins: we've created a survey to gather requirements and would love to hear your thoughts. The linked discussion includes background information and potential approaches we could take. github.com/oxc-project/...

I'm starting "This week in Oxc" to improve roadmap visibility. Feel free to subscribe to this thread. github.com/oxc-project/...

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

There have been a number of bug fixes and improvements to the editor experience for oxlint recently. If you have run into any bugs or issues with the `oxc` extension in VS Code, we would be interested to hear about it: github.com/oxc-project/...

Want to follow all updates + people involved in and around @voidzero.dev projects here on Bluesky? Then make sure to check out our starter pack! go.bsky.app/Sbpuppb

Oxlint has now reached a beta version! It's faster than ever, has over 500 rules built-in and we are working on adding lots more features. We are also working towards supporting custom plugins as well 🙏

500 Oxlint rules. What a remarkable achievement by everyone who has contributed to OXC. It was only 11 rules when I completed the prototype back in June 2022.