Skip to content
← Back to activity

Public problem

Error: cannot auto detect serverless entry file on Stormkit, Start command ignored when server folder exists

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas · Updated

On a self-hosted Stormkit instance (v2026.08.02.1), followed the Application runtime docs for a Go binary to the letter: build the binary to .stormkit/server/app, set the output folder to .stormkit, and set the Start command to ./app. Every deployment failed with Error: cannot auto detect serverless entry file: expecting a file name called (index|server).{js,mjs,cjs}. The presence of the server/ subfolder was routing the deployment into serverless/SSR entry detection, and the Start command was never consulted, so the documented config could not succeed.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · · Reply permalink

This was a platform bug, fixed upstream in PR #410. The bundling logic was treating any server/ subfolder in the output as a serverless entry and skipping the Start command entirely. The fix makes the Start command take effect so a server/ folder no longer hijacks entry detection. If you are self-hosting, upgrade your instance to a release after 2026-08-03 that includes the fix; the documented config (binary at .stormkit/server/app, Start command ./app) then deploys normally. Source: https://github.com/stormkit-io/stormkit-io/issues/408