Well, yes to both. The initial reason why I started the engine because I wanted something that could run typescript natively. For now it just does type-stripping and some transformations to run react code.
For source mapping, some errors are converted, mainly syntax ones, but there are no real conversions for errors arbitrarly thrown in the engine.
The tooling, mostely no. But if people want it I don't see any issue why I should not do that.
Zuck said by himself that they will release the weights of Muse Spark 1.2, and now we only get that one. At least they bench similarly bad for the size on Artificial Analysis
Oh what? That was not on my bingo card for 2026. Mold already was incredible when it still was in C++ and I assume it is even better now that it is in rust
They're effectively ready to use even if experimental; the migration path is typically pretty painless when features are stabilised and the codemods get you most of the way. There's a couple of missing features for them but if you don't need those then it's not a problem.
The idiomatic way to do data fetching in stable SvelteKit is via load functions.[0]
They still do a good job and allow you to cache the results and invalidate that cache, but they are at a route/layout level rather than at a component level, which is what remote functions solve.
I think there are a few more. Especially cranelift, but I would not use it for production stuff and it is missing a lot of llvm intrinsics that will just trap if you are trying to use them. But for most it seems to be just fine for regular dev builds with a HUGE speedup.
The tooling, mostely no. But if people want it I don't see any issue why I should not do that.
reply