SvelteKit SSR is a very good pair to Python backends, like FastAPI.
Can you expand? I don't get how you can use SSR with another language than Node. I always thought one has to use the static adapter.
Re:SvelteKit 1.0
by buttersbrian on Wednesday December 14, 2022 @11:50PM
(#33995351)
the backend svelte (node) can actually make calls to the separate api server and render a 'fuller' page to the client on page load.
I believe this is what is meant.
Requests are routed reverse proxy (Caddy) -> Vite (SSR) -> Python (Pyramid).
SSR calls your backend APIs and renders templates.
Example from SvelteKit page.ts here:
https://github.com/tradingstrategy-ai/frontend/blob/master/s...
Some remarks
- page.ts is routed by Vite for every HTTP request for SSR and then it will fetch() data over backend API
- If rendered in the client, fetch() hits directly the backend API
- Both cases the template is rendered using the same logic (Svelte HTML templating, CSS, JS)
- You are going to need a template language any cases, like Django's one. Alternative way to think this is that SvelteKit is just a super powerful template engine.
Do i get this right, using SvelteKit SSR frontend node server and it communicates with backend FastAPI server via json. This is nowadays called a normal stack oO. (by the way i like Svelte but SvelteKit makes only sense if you stay in JS land, and i'm not willing to jump ship from python to js/ts ;))
I tried htmx and so far i really like it and the + is i just have "one" backend.
Sveltekit + TailwindCSS + FastAPI has made it super easy to whip up functionality and have a fine-tuned approach as well.
As someone else said, the "I CAN'T BELIEVE IT WAS THAT EASY" is an ongoing sentiment whenever I use it.
Looking forward to seeing it grow and gain more popularity