Using Hono with SvelteKit - Full type-safety with RPC

[brunoti]

Hi guys! I wrote a post about using Hono with SvelteKit! Accepting feedbacks!

dev.to/bop/using-hono-with-sveltekit-full-type-safety-with-rpc-2h7

[Oceanbao]

Thanks @brunoti for sharing your work on this stack as I've been looking into type-safe Hono backend.

May I ask what do you think it's the extra benefit using Hono as backend with SvelteKit this way? As I understand, you can also get full-type-safety using SvelteKit's backend with zod validations.

I was under the impression that the main reason to Hono as standalone backend is the edge serverless integration with Cloud providers and lightweight framework as a whole. But SvelteKit's backend api functions can also be deployed by some serverless cloud provider as edge functions, e.g. Cloudflare or vercel.

So I was wondering what's the extra benefit injecting Hono layer in SvelteKit project as backend.

Thank you so much.
Ocean

[Rykuno]

Just like NextJS, SvelteKit's backend is barebones. You don't get all the very nice features you get with a fully independent backend library. Also, if you ever want to break out your sveltekit/api into two seperate services, its about 3-4 lines of code extra.

I created a boilerplate to do the same thing a while ago and have written the benefits here https://github.com/Rykuno/Sveltekit-BYOB-Template

TLDR; gives your sveltekit backend type-safety, ability to scale independently, breakout if needed easily, and the benefits of a full backend library at your disposal.

[Oceanbao]

Brilliant! Thank you for sharing that stack, I fully concur with all the choices. And thumbs up for the project structures!

[KelechiOdom10]

@Rykuno I just found this, and I absolutely love it. Thank you! I was wondering if we could have a section on deployment in the README

[Rykuno]

@Rykuno I just found this, and I absolutely love it. Thank you! I was wondering if we could have a section on deployment in the README

For sure. I'll push an update soon but I've since moved away from coupling my frontend/backend together since the workarounds get annoying when dealing with multi-tenant apps, introducing queues/workers, or having something like a discord/mobile app paired with it.

Essentially it was only good for relatively simple apps lol. I'll update it soon with how I've been building as of lately with render and railway deployment configs.