sveltekit-starter VS sveltekit-prisma

I had this on my starred repos, I hope you find it useful!

For Endpoints, I'd recommend checking out this example for a good idea on how they're used. If you're gonna be transforming the external API data, you can do it in the Endpoint. Speed really hasn't been a concern for me, even deployed on Cloudflare Workers. Here's one of my endpoints, for an example of how I use and abuse endpoints lmfaoo.

I saw that but it's not really designed for component libraries. It's also SSR. I'm looking to do client side rendering. Really good template though. Will probably take inspiration from it when moving past components.

Solution: Add the following to your package.json scripts section then push to vercel. Your package.json should look similar to this. More info about this here and here. "postbuild": "cp node_modules/@prisma/engines/query-engine-* .vercel_build_output/functions/node/render/;cp prisma/schema.prisma .vercel_build_output/functions/node/render/"

I may recommend checking prisma, it's nice piece of tech, easier to use than raw sqlite3 and probably works without much hassle. Might wanna check this sample too https://github.com/mikenikles/sveltekit-prisma

With a few modifications to a default SvelteKit demo app, we managed to configure Prisma to persist todo items. There is of course a lot more you can do with Prisma, and with SvelteKit for that matter. The source code at https://github.com/mikenikles/sveltekit-prisma should get you a long way towards your own web app.