TheAlexLichter

5 ms·

1.
by TheAlexLichter 2mo ago
That did happen! https://github.com/oxc-project/oxc-css-parser/issues/92#issu...
2.
by TheAlexLichter 3mo ago
I am using Vite+ for CLIs as well, yes. You don't use Vite as dev server then but lint, format, task running and caching is still there!
3.
Vite 8.1 is out with an experimental full bundle mode(vite.dev)
1 points by TheAlexLichter 3mo ago|0 comments
4.
by TheAlexLichter 3mo ago
Not really. The claim is that nothing will change regarding the OSS projects.
5.
by TheAlexLichter 4mo ago
Vite is a multi stakeholder team. How would that happen?
6.
by TheAlexLichter 4mo ago
IMO perfect for Vue (and similar for Vite). All the talented folks working together.
7.
by TheAlexLichter 4mo ago
Just use Vite Plus (viteplus.dev)
8.
by TheAlexLichter 4mo ago
1) The blog post mentions "acquisition" multiple times. 2) VoidZero joins Cloudflare is still correct. Nobody forced anyone to accept a deal and do so
9.
What's New in ViteLand: Oxfmt Beta, Vite 8 Devtools and Rolldown Gains(voidzero.dev)
2 points by TheAlexLichter 7mo ago|0 comments
10.
by TheAlexLichter 7mo ago
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://voi
11.
by TheAlexLichter 7mo ago
There will be more
12.
by TheAlexLichter 7mo ago
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
13.
by TheAlexLichter 7mo ago
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 compet
14.
by TheAlexLichter 7mo ago
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.
15.
by TheAlexLichter 7mo ago
As said in another comment: Curious to see what you are coming up! Talk is cheap
16.
by TheAlexLichter 7mo ago
> 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 b
17.
by TheAlexLichter 7mo ago
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 indee
18.
by TheAlexLichter 7mo ago
Not really.
19.
by TheAlexLichter 7mo ago
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. w
20.
by TheAlexLichter 7mo ago
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 compile
21.
by TheAlexLichter 7mo ago
The good part is that the new tools do replace the old ones, while being compatible. The pattern is: * Rolldown is compatible to Rollup's API and can use most Rollup plugins * Oxlint supports JS plugins and is ESLint compatibel (can
22.
by TheAlexLichter 8mo ago
Mentioning SWC and ESBuild but missing Rolldown ( https://rolldown.rs/ ) here seems like a miss.
23.
Vite 8 Beta(vite.dev)
9 points by TheAlexLichter 10mo ago|1 comments
24.
VoidZero's ViteConf 2025 Recap(voidzero.dev)
1 points by TheAlexLichter 11mo ago|0 comments
25.
by TheAlexLichter 11mo ago
Take a look at workspace mode for that! See e.g. https://github.com/vue-macros/vue-macros/blob/main/tsdown.co... for reference.
26.
by TheAlexLichter 11mo ago
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.
27.
by TheAlexLichter 11mo ago
Appreciate that! Prices and details will be known closer to launch, so stay tuned
28.
by TheAlexLichter 11mo ago
Consulting doesn't scale though and draws resources from development itself, harming both the OSS and the business side. All functionality as part of OSS projects will stay there. OSS projects such as Vite, Vitest, Rolldown and Oxc wil
29.
Vite+(voidzero.dev)
10 points by TheAlexLichter 11mo ago|0 comments
30.
by TheAlexLichter 11mo ago
Take a look at the formatter RFC https://github.com/oxc-project/oxc/discussions/13608

More ›