# Configure build and start for SvelteKit

Configure build and start for a SvelteKit app on Ample. Use @sveltejs/adapter-node and start the build with node build; it reads PORT and HOST. Ample detects the runtime, installs dependencies, runs the build when present and starts the app on the node-22 template behind a public HTTPS URL.

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

## You need

- A package.json with build and start scripts  
- A server that listens on process.env.PORT and 0.0.0.0  
- An Ample account token with servers:write

## Exact tested configuration

build
```bash
npm run build --if-present
```
install
```bash
npm install
```
runtime
```bash
node
```
sizes
1vcpu-1gb
start
```bash
npm run start
```
template
node-22

## Steps

1. **Make the start command bind correctly.** Use @sveltejs/adapter-node and start the build with node build; it reads PORT and HOST.

2. **Deploy.** Run the existing synchronous deploy once from the project directory and read the result. Exit 0 is live, 1 is failed, 2 needs an answer first (a preflight question). Re-running with no change is a content-addressed no-op.

```bash
$ ample deploy . --name <app-name> --public --format json
```

3. **Verify.** Fetch the live URL and run the success checks below. On failure read the build log, then the runtime log, fix the cause and deploy again; do not blind-retry.

```bash
$ ample logs <deployment_id> --kind build
```

## How it was checked

✓ page or root route responds · http get/ → "ample canary sveltekit node adapter"

## Evidence

1. November 5, 2026 · canary run  
   SvelteKit app with adapter-node deployed on node-22 and rendered the expected page.

## Tested examples

- **sveltekit-node-adapter canary.** SvelteKit with adapter-node.

## What it doesn’t cover

- Verified on the node-22 template at s-1vcpu-1gb.
- Use @sveltejs/adapter-node.
