SvelteKit app restarts because a startup path is undefined
The application started but did not answer on any port it publishes. The deploy log has the per-port result; a worker or queue-only app can ignore this. | The application is restarting, not running. Docker reports app (Restarting (1) 30 seconds ago). Nothing answered on any published port because the process keeps exiting. Read the container output with container_service_logs; the reason it exits is there.
TypeWarningAn issue PanelAlpha Engine catches around a deploy that does not break it. It tells you, before or after, that you may need to do something.
Seen1 times
WhereSveltekit
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The build completed, but the SvelteKit server crashes during startup in a server hook. Its startup code passes an undefined value to path.join, likely because a required environment variable or configuration path is missing. The container then restarts continuously, so port 3000 never becomes available.
What the log looks like
Deploy log
Application compiledStarting application (docker compose up -d)Health check: http://[ip]:3000/ did not answer — Failed to connectTypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined at Object.join (node:path:1305:7) at onServerStartup (.../hooks.server.js:87:26)Node.js v20.20.2app-1 ... [panelalpha] start: serveapp-1 ... Docker reports app (Restarting (1))