Frameworks

SvelteKit on Stackap

Stackap does not recognize SvelteKit yet: the @sveltejs/kit dependency keeps a project off the static path, and it runs only if you give it a start script or a Dockerfile.

How Stackap recognizes SvelteKit

The dependency @sveltejs/kit excludes a project from the static-site path, since SvelteKit decides at build time whether it produces static pages or a server, through an adapter. Stackap does not read the adapter. With the static path ruled out, detection looks for a root index.html, finds none, and then for a start script.

What Stackap builds

The route that fits Stackap best is the Node adapter. It writes a self-contained server into a build folder, which you start with node build. Put that command in a start script, make sure the server reads PORT, and Stackap will build the project and run it as a Node app.

A SvelteKit site built with the static adapter writes finished pages, often into a build folder with an index.html. Stackap would not take it down the static path because of the dependency check, but a Dockerfile of your own that copies those pages into a small web server works regardless.

Either way the same health-check and port rules as every other Node app apply.

What a SvelteKit project needs

The Node adapter and a start script, or a Dockerfile.
The server listening on PORT.
A route that answers a health check.
Public variables using SvelteKit's public prefix, never secrets.

Verification status

Verification pending. No SvelteKit project has been built on Stackap. The two routes above come from reading how detection and the adapters work.

Early-access scope

SvelteKit is not a supported framework today.
The static adapter's output is not detected automatically, because the dependency check comes first.
The generated build image uses Node 24, so a project that needs an older Node should bring its own Dockerfile.
Adapters for edge and serverless platforms have no equivalent here.
No persistent disk, and no process other than the one server.

Questions

What about Svelte without SvelteKit?

A Svelte app built with Vite alone is a single-page app, and it takes the Vite path like any other.

Which adapter should I use?

The Node adapter, with a start script, is the closest fit. It is the route most likely to work, but it is untested here.

Does it work with the static adapter?

Only through your own Dockerfile today. Detection will not take it down the static path.

Stackap is in early access. Tell us what you run and we will reply with a straight answer about whether it fits.

Ask for an invitation

Last updated 2026-10-03.