SvelteKit · Buckets Implementation

SvelteKit with KERNSTACK buckets

A SvelteKit app ships on KERNSTACK as files in a bucket: the app builds to static output (adapter-static), the build output lands under the app’s bucket prefix on every deploy through the app’s build hook, and a gateway prefix route serves it. There is no frontend host to configure because hosting is a declared consequence of the build, reviewed in the same diff as the code.

Object Buckets stack.json IaC

Talk to us Read Technical Documentation → Software Lifecycle Cloud →

SvelteKit Buckets

Mechanics worth naming: on deploy, the app’s declared build runs, output is copied into the bucket’s seed path, and the route serves the new version as one unit. Rollback is redeploying the previous declaration; the old “which bucket did CI upload to?” archaeology cannot happen, because the bucket is a stack resource with a name in the manifest.

SvelteKit’s prerendering strengths carry straight over: fully static marketing pages, prerendered docs, and an SPA shell (fallback_mode: "spa") for the application proper. Canonical redirects collapse .html and slash variants to one URL by default — the SEO detail hand-rolled hosting setups routinely get wrong.

When the app needs data, it calls the project’s functions and workers through routes on the same hostnames — same-origin by construction, CORS ceremony mostly absent. Frontend and backend stop being separate deployments that discover each other at runtime.

CLI

Plan SvelteKit Buckets, then deploy.

Terminal — CLI workflow kernstack cli

kernstack plan
kernstack plan
kernstack deploy

Docs for SvelteKit Buckets. Buckets on the platform.

sveltekit-buckets.txt SvelteKit

# create the app under apps/web (SvelteKit with @sveltejs/adapter-static);
# apps build on deploy — no separate frontend pipeline
kernstack plan     # shows the app build and bucket publish
kernstack deploy

stack.json — SvelteKit + buckets plan · deploy

{
  "gateway": { "routes": [{ "name": "web", "type": "prefix",
      "target": { "kind": "bucket", "name": "web" }, "cdn_enabled": true,
      "fallback_mode": "spa" }] },
  "resources": { "buckets": [{ "name": "web" }] }
}

FAQ

Frequently asked questions

Which SvelteKit adapter should we use?

adapter-static. KERNSTACK serves the built output from a bucket; server-side rendering belongs in a Node.js worker if a route genuinely needs it, with the static app calling it.

How do deploys avoid stale pages?

The build output replaces the published set as one deploy unit, and canonical redirects keep one URL per page. Teams add cache headers per asset class in app configuration when aggressive caching is wanted.

Can the SvelteKit app call our API same-origin?

Yes. API routes (functions or workers) and the app’s prefix route coexist in the gateway, so fetches are same-origin and private routes can demand the project’s API key.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Ship your stack on the Software Lifecycle Cloud.

Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.

Talk to us See pricing & credits →