Claude
0512428601
adapter-auto doesn't produce a runnable standalone server when it can't detect a supported hosting platform (Vercel/Netlify/Cloudflare/etc.) — this is a self-hosted app with no such platform, so builds were silently missing a real server output. Swapped to adapter-node, which builds to build/index.js: a persistent Node server that reads PORT/HOST/ORIGIN at runtime, exactly what a reverse proxy needs to point a domain at. Added a README section covering the full path: building/running both apps as plain Node processes, the env vars each needs, and the Nginx Proxy Manager side (proxy host + Custom Locations for /api and /media under a single-domain, path-routed setup, or a simpler two-domain alternative). Verified live: the adapter-node build actually serves pages and correctly picks up ADMIN_PANEL_ENABLED via `node --env-file=.env build/index.js` (SvelteKit's $env/dynamic/private reads process.env directly in production, unlike the vite-dev-time gap from the previous fix).
sv
Everything you need to build a Svelte project, powered by sv.
Creating a project
If you're seeing this, you've probably already done this step. Congrats!
# create a new project
npx sv create my-app
To recreate this project with the same configuration:
# recreate this project
npx sv@0.16.2 create --template minimal --types ts --install npm frontend
Developing
Once you've created a project and installed dependencies with npm install (or pnpm install or yarn), start a development server:
npm run dev
# or start the server and open the app in a new browser tab
npm run dev -- --open
Building
To create a production version of your app:
npm run build
You can preview the production build with npm run preview.
To deploy your app, you may need to install an adapter for your target environment.