Back to blog
engineering

We Deployed 17 Real Repos Before Launch. Here Is What Broke.

By Daniel

We Deployed 17 Real Repos Before Launch. Here Is What Broke.

For months every app RunMist deployed was one of ours. They all worked. They also all had the same shape: same runtime, same package manager, same layout.

Then we deployed one real outside repo, an old Gatsby site pinned to Node 12, and spent two days on it. The repo's Node pin was ignored. Yarn was missing. The build ran out of memory. Static sites could not be hosted at all.

Our apps never hit any of that, because they are all built the same way. Customers' repos are not. So before telling anyone about RunMist, we picked a fixed set of real repos and deployed every one of them through the product, on a real server.

The set

Templates from Vercel's gallery, one per category, because that is what someone leaving Vercel actually has: a Next.js app, the commerce template, the SaaS starter, the AI chatbot, the multi-tenant platforms kit, the dashboard tutorial, a blog. Then the non-Next ones: Astro, SvelteKit, Express, Hono, Vite, Docusaurus, and two Turborepo monorepos.

Between them they cover npm, yarn 1, yarn 3, pnpm and bun; old and current Node versions; a monorepo; an app in a subfolder; static sites; server-rendered apps; and an API with no home page.

A repo passed only if all of this was true, through the product and not a local build:

  1. Import works, and the framework, kind, package manager and Node version are detected with no manual edits.
  2. The first deploy succeeds.
  3. The address serves the right content, checked by a string from the app, not just a 200.
  4. A push redeploys it, and a rollback works.
  5. For static sites, a missing file returns 404 and not the home page.

What broke

Host-only adapters. The Astro and SvelteKit templates ship with a Vercel adapter. They build fine and then do not run anywhere else. RunMist now spots a host-only adapter at import and tells you which one to switch to, before you deploy.

Apps with no start command. Vercel's Express and Hono examples export the app and let the platform run it. On a server there is nothing to start. The form now warns when a repo has no start script, and says what to add.

Package manager versions. A repo with no pinned pnpm got the newest major, which could not read its lockfile. A monorepo pinned pnpm 8 but shipped a pnpm 9 lockfile. RunMist now matches the package manager to the lockfile, and says so when the pin and the lockfile disagree.

Monorepos. The dashboard tutorial keeps five apps in subfolders, each with its own lockfile, under a root that only lints. Detection saw the root and stopped. It now lists the nested apps so you can pick one.

Node versions. The repo's own pin is now honored, from Node 12 up.

Frameworks we did not know. Docusaurus was not detected at all. It is now.

Our own wording. The rollback button said "instant". For some projects it rebuilds, which takes 20 seconds. We fixed the label, not the stopwatch.

Not everything is fixed. Wildcard subdomains for multi-tenant apps are not supported yet, and a template that depends on Vercel-only services keeps that dependency: it deploys, and the gap is written down.

What it looked like at the end

All 17 projects ran on one 4 GB server at the same time. First deploys took between 13 seconds (Express) and about two minutes (a Yarn 3 monorepo). A new server went from click to ready in 2 minutes 24 seconds.

Then we load-tested that server with all 17 apps still running.

Why tell you this

Because "it works with Next.js" means little until someone has tried your Next.js. The list above is what we tried, and the failures are the ones you will not hit. When you find the next one, it gets the same treatment: reproduced on a real server, fixed, and added to the set.