#SilverBullet 2.6 released!

This is a big one. Under the hood, the entire TypeScript/client codebase has migrated from Deno to Node.js (now using vitest for tests), with bundle size optimizations via chunked ESBuild builds and JIT loading of larger modules. There's a brand new (experimental) Runtime API and accompanying CLI that let you programmatically drive a remote SilverBullet server, evaluating Lua expressions among other things. And more!

https://community.silverbullet.md/t/silverbullet-2-6-released/4024?u=zef

SilverBullet 2.6 released!

SilverBullet 2.6 is a big one. Under the hood, the entire TypeScript/client codebase has migrated from Deno to Node.js (now using vitest for tests), with bundle size optimizations via chunked ESBuild builds and JIT loading of larger modules. On top of that, there's a brand new (experimental) Runtime API and accompanying CLI that let you programmatically drive a remote SilverBullet server, evaluating Lua expressions, running scripts, and fetching console logs against a full client running in head...

SilverBullet Community
@silverbulletmd interesting. Usually its node to deno! What made the change? I have no real investment in either nowadays, but im curious.
@michael First of all, the only remaining use of Deno was to build the frontend. The backend had already been rewritten to Go a while ago. For the frontend, the node.js ecosystem is richer and more stable. I've spent many an hour fighting Deno regressions over the years and it's not really worth it. I also am not super sure about Deno's future to be honest. I don't get a sense they're doing so well as a company (lay-offs recently). Node.js will be around for a long time, so it's the safer bet.