Post

Ilja
@fubits.dev

This is quite a milestone for the Svelte ecosystem! Thereby also discovered that one SvelteKit adapter for Bun (there are at least four) just had a full rewrite! github.com/gornostay25/...

github.comRelease SvelteKit Adapter Bun v1.0 · gornostay25/svelte-adapter-bunAdapter for SvelteKit apps that generates a standalone Bun server. Full rewrite More examples
Ben McCann@benmccann.com

svelte.dev/packages is now live! It's a convenient and easily discoverable place to find a sampling of high quality packages in the ecosystem. We hope it will give confidence in the Svelte ecosystem to newcomers and help them get started more easily.

svelte.devPackages • SveltePackages for your Svelte and SvelteKit apps
Kevin Åberg Kultalahti
@kevinak.se

I have to admit, the bun adapter is not selling itself well. The node adapter works very well. I assume it adapts the output to use bun.serve instead of polka or whatever the Node adapter uses? 🤔

Ilja
@fubits.dev

ah, sorry! So at least in my experience with Coolify, Bun uses like 1/3 of the RAM that Node consumes. Don't nail me down to the exact numbers, but it's like 200 MB vs Node's 500+ MB. There are many more perks (like Bun being all-in one: package manager + bundler + runtime AND a single executable)

0 reposts1 like

Ilja
@fubits.dev

And then there are Bun's native drivers for S3, SQLite, Postgres etc. So in theory for simple CRUD fullstack you need: - Bun - SvelteKit - 1 SQLite file Done (but with the smallest memory footprint possible). I'm not die-hard benchmarking performance, but it should be more performant as well.

Kevin Åberg Kultalahti
@kevinak.se

Ok - performance sounds like the differentiator then, because I can already use the SQLite driver and S3 driver with the Node adapter :) It’s actually been great! I love that the debugging story has gotten better as well, debugging SQLite issues was a major headache before iirc