[pier25]

I started using Svelte a couple of years ago and I love it. Very quickly it became the only client side solution I want to use.

Can't say the same about SvelteKit though. I've tried it a couple of times and it's just not fot me. It's really a tool built around a client side library and it shows (instead of being a backend framework).

[Hugsun]

I've been using it professionally for some time and find it pretty nice. What are your frustrations with it?

[pier25]

It's severely lacking in the backend but I guess this is more of a general issue with all so called full stack JS frameworks.

Specifically with SvelteKit the big deal breaker is routing. I also find the whole +page.svelte stuff to be a usability nightmare since I barely use the file explorer to move around a project and instead use fuzzy search. Unfortunately SvelteKit is pretty unflexible so you either love it or hate it.

It's really weird that I agree 100% with all the decisions regarding Svelte itself and how it's evolving (runes etc) but SvelteKit is just a big nope from me.

[robwg]

I wouldn't judge any JS framework like SvelteKit or Next.js on its lacking in the backend. They have a server to handle frontend problems, not solve your backend problems.

[efilife]

Previous versions of SvelteKit didn't have this +page handicap. Try older versions if it's still possible and you will love it

[pier25]

Wouldn't make much sense to invest time into an abandoned and unfinished version of SvelteKit.

[efilife]

It's just so you can see how good it was