SvelteKit ecommerce, in production shape.
What you get if you want the framework rather than a platform: real routes, real load functions, real adapters — and a commerce layer you can point anywhere.
The SvelteKit parts
Built on the framework rather than around it.
Rendering
Server-rendered first paint for crawlers and cold loads, then client-side navigation. Per-route control rather than one global setting.
Hooks
hooks.server.ts resolves the store and applies backend config on the server; hooks.client.ts does the same
in the browser, which production needs.
Adapters
Node adapter for npm start, plus zero-config Netlify and Vercel deploys and a published Docker image.
Aliases
$lib/core/services is the single commerce entry point; the kitcommerce.config alias resolves the active
backend at build time.
Routes that already exist
Not a template with three pages.
/
/[slug]
/products
/products/[slug]
/checkout/cart
/checkout/address
/my/orders
/my/orders/[id]
/my/wishlist
/my/profile
/my/addresses/[id]
/auth/signup
/auth/forgot-password
/auth/reset-password
/blog
/blog/[slug]
/contact-us
/faqs
/p/[slug]
/privacy-policy
/refund-policy
/shipping-policy
/terms-and-conditions
/sitemap.xml
/health
Start with your backend.
Clone it, point it at your API, and describe the store you want.