n nesly
Menu
TR Sign in

Deploy SvelteKit

How nesly detects, builds and serves a SvelteKit project — and the two commands that put it on a live URL.

Deploy SvelteKit on nesly

A SvelteKit project is served statically or run as a server, depending on how the project is configured.

cd your-project
nesly deploy --yes

The first deploy creates the project and prints the live URL; after that, nesly deploy is enough.

How detection sees it

  • A package.json depending on @sveltejs/kit is detected as SvelteKit.
  • Only @sveltejs/adapter-static produces a static site (served from build/); every other adapter produces a server, which runs as a container.

When detection is not what you want, say it yourself: build and start commands, root directory and output directory live in nesly.toml committed next to the code — see builds.

Worth knowing

  • With adapter-node, the server reads PORT from the environment — the platform sets it; do not hard-code one.
  • Attach a managed database with nesly addon add postgres (or mssql) — connection env vars are injected on the next deploy.
  • When a deploy fails, nesly diagnose reads the logs for you and names the fix.

Full walkthrough: get started. Custom domains, backups, GitHub deploys and the rest of the reference: nesly CLI.