5 ms·
I agree with you, but what that actually looks like can vary. Personally, I found maintaining a second backend only codebase and hitting it from the SvelteKit
by dimmke 3y ago
I agree with you, but what that actually looks like can vary.
Personally, I found maintaining a second backend only codebase and hitting it from the SvelteKit backend to be really cumbersome.
You can write controllers and even an API and keep it in its own folder system.
- Ins43b 3y agoI'm currently doing this with Next.js with a "custom server". Allows for sharing TypeScript interfaces/types and the express instance quite easily. It's just one big vscode project. But custom servers are frowned upon and will probably disappear in future versions which will make things slightly more complicated.