Vite 8 is in beta, so you can try it out already. See https://voidzero.dev/posts/announcing-vite-8-beta

Rolldown is in RC, meaning no more breaking changes (except for experimental features). See https://voidzero.dev/posts/announcing-rolldown-rc

There will be more

I personally met a lot of folks who care about both quite a bit.

But to be fair, besides the usual patterns like tree-shaking and DCE, "runtime performance" is really tricky to measure or optimize for

For a couple of reasons:

* You need have a clean architecture, so starting "almost from scratch" * Knowledge about performance (for Rust and for build tools in general) is necessary * Enough reason to do so, lack of perf in competition and users feeling friction * Time and money (still have to pay bills, right?)

Love that fact that you don't need anything ts-node/tsx like if you have erasable syntax only. Other than that, there is https://github.com/oxc-project/oxc-node too.

Not really.

As far as I'm aware oxlint only supports plugins for non type aware rules, and type aware rules themselves aren't fully stable because it relies on a fork of tsgo.

That is correct, every rule with a custom parser (e.g. vue/svelte/astro tempaltes) and also type-aware rules can't be used as JS plugin.

Type-aware rule are indeed not marked as stable but work like a charm. tsgolint is indeed tsgo + shims + some works, but that won't change soon as tsgo won't have a JS API for a while.

So you really think everyone in JS should have to learn Rust or else be excluded from sharing in the ownership of their critical infra..?

1) This is not what I said, no

2) With AI, languages and syntax matters even less nowadays.

3) There have been a good amount of contributors (e.g. for Oxc) that came out the JS world, so it isn't impossible

4) Realistically, the avg. web dev does not contribute to tooling internals, maximum custom rules or similar. The concepts are a bigger "hurdle" than the lang.

That still leaves you admitting that only a small fraction of the served community can really contribute. You'll need to keep all the best benefits of your work for the Plus users or else there would be no reason to buy Plus and no way to keep paying the few to do all the work for the many.

You're stuck telling people what they can't have (and shouldn't want) while I'm now in a position to just give people what they want. I admire the people who work there, but you need a new business model and fast because I am unequivocally going to collapse your current one.

> That still leaves you admitting that only a small fraction of the served community can really contribute.

Not really (see above).

> You'll need to keep all the best benefits of your work for the Plus users or else there would be no reason to buy Plus and no way to keep paying the few to do all the work for the many.

No, won't happen that way.

> You're stuck telling people what they can't have (and shouldn't want) while I'm now in a position to just give people what they want.

Didn't see any software of yours yet, only big talk so far sadly! Besides that, VoidZero will also be in a position to just give people what they want

VoidZero is betting I'm just talk, ok, that's fair. But the way you say it makes me think that your evaluation of me is mostly on hearsay, because if you had actually tried to find out how serious I am I suspect you'd be less flippant. You're welcome in the Discord!

e: ahhh frick this is just stupid AI spam for this dude’s project.

Supports… some ESLint rules. It is not “easy” to add support to Oxlint for the rules it does not.

The projects at my work that “switched” to it now use both Eslint and Oxlint. It sucks, but at least a subset of errors are caught much faster.

Vite+ is not “this dude’s project”, it’s made by the team that makes all the tools discussed in this article.

Yeah, no. Real human here.

Oxlint does support core rules out of the box but has support for JS plugins[0] as mentioned. If you don't rely on a custom parser (so svelte or vue component for example) things just work. Even react compiler rules[1].

[0] https://oxc.rs/docs/guide/usage/linter/js-plugins.html [1] https://github.com/TheAlexLichter/oxlint-react-compiler-rule...

Definitely read AI tonality into the earlier comment, noticed it didn't call out your relationship to it, then saw that you had a comment history plugging it, and made assumptions.

My apologies. I'll follow through to the links next time.

So as long as you only need the pre-installed software it's a great device eh. I'm the PC to your game console here. Parser extension? Piece of cake for us. Heck just to showboat we actually extended our es6 parser from our es3 parser, and then implemented each later standard as an extension of the earlier one. We're able to run parsers for pretty much any programming language, and making them super easy to write. We can do cross-language transforms with ease. We can be our own system of version control! We're going to be a real threat to GitHub. VoidZero is not even trying to do this stuff. Your vision is just so... small.

As said in another comment: Curious to see what you are coming up! Talk is cheap

Mentioning SWC and ESBuild but missing Rolldown (https://rolldown.rs/) here seems like a miss.

Or Rspack (https://rspack.rs/) which is intended to be a drop-in Webpack replacement

Take a look at workspace mode for that! See e.g. https://github.com/vue-macros/vue-macros/blob/main/tsdown.co... for reference.

Good point! Will improve this.

Think of it as in opinionated Rolldown-"preset" for libraries. It will be used as the foundation of Vite's lib mode revamp.