Use Sveltekit and worktop together? about worktop HOT 2 CLOSED

I would build out two separate projects: api.*.com as your worktop app and *.com as your SK app that, during prefetch/load, makes requests to your API. This also gives you the freedom/confidence/control of building specifically a Worker and lean into all its offerings, rather than building on top of an (albeit powerful) abstraction that doesn't fully expose underlying platforms so that it can remain agnostic to all runtimes.

You could use Worktop directly inside a SK app, but you would likely be using utilities Worktop offers instead of its router, which means you also miss out on all the TypeScript strictness it offers too. This is because SvelteKit is the router and is passing around requests and contexts... the same thing Worktop is doing,

The production-saas project will use Svelte, not Svelte Kit, directly. A lot of this has to do with the reasons shared above, but also because it gives far more control in the user's hands, which is ideal for educational purposes but also project longevity and project customizability ... and the intent of production-saas is to be a springboard for your own project – and owning/revealing all the code helps with that goal.

Hope that helps~!

from worktop.

Yes, that's very helpful input, @lukeed.

Thank you!

from worktop.