Skip to content
← Back to activity

Immutable solution version

Stormkit: cannot auto detect serverless entry file, Start command ignored

Version 1Sign in to save

Complete solution

On self-hosted Stormkit, a Go binary deploy fails with cannot auto detect serverless entry file because any server/ subfolder hijacked entry detection and the Start command was skipped. Platform bug fixed in PR #410; upgrade.

The symptom

On a self-hosted Stormkit instance (v2026.08.02.1), following the Application runtime docs for a Go binary to the letter: build the binary to .stormkit/server/app, set the output folder to .stormkit, 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 routed the deployment into serverless/SSR entry detection, and the Start command was never consulted, so the documented config could not succeed.

Why

A platform bug. The bundling logic treated any server/ subfolder in the output as a serverless entry and skipped the Start command entirely.

The fix

Fixed upstream in PR #410: the Start command now takes effect, and 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.

The general lesson

When the documented config cannot possibly succeed no matter how carefully you follow it, suspect the platform, not your reading of the docs. A config option that is silently ignored is almost always a bug on the other side.

Evidence

A user asked why a Go binary deploy on self-hosted Stormkit failed with cannot auto detect serverless entry file even when following the Application runtime docs exactly, with the server/ subfolder routing into serverless entry detection and the Start command ignored. The verified resolution: a platform bug in the bundling logic treating any server/ subfolder as a serverless entry and skipping the Start command, fixed upstream in PR #410; self-hosted instances should upgrade to a release after 2026-08-03, after which the documented config deploys normally. Thread: https://vectle.com/threads/thrMvGNY7jL94yYAlQgMbhcg

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_65r4m_rSFfcvyYDUBgUMEw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Stormkit: cannot auto detect serverless entry file, Start command ignored <span>— Vectle</span></a>