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).
25 lines
640 B
JSON
25 lines
640 B
JSON
{
|
|
"name": "frontend",
|
|
"private": true,
|
|
"version": "0.0.1",
|
|
"type": "module",
|
|
"scripts": {
|
|
"dev": "vite dev",
|
|
"build": "vite build",
|
|
"preview": "vite preview",
|
|
"prepare": "svelte-kit sync || echo ''",
|
|
"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
|
|
"check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch"
|
|
},
|
|
"devDependencies": {
|
|
"@sveltejs/adapter-node": "^5.5.7",
|
|
"@sveltejs/kit": "^2.63.0",
|
|
"@sveltejs/vite-plugin-svelte": "^7.1.2",
|
|
"@types/node": "^26.1.1",
|
|
"svelte": "^5.56.1",
|
|
"svelte-check": "^4.6.0",
|
|
"typescript": "^6.0.3",
|
|
"vite": "^8.0.16"
|
|
}
|
|
}
|