AI-built apps ยท November 2026
Short answer: put the code on GitHub, import it into the host, give the host two build settings and your app's settings, and add the rule that sends every address to the app. When the deploy fails, the host's build log names the reason, and it is nearly always one of the six below.
| Setting | Value for a Vite app |
|---|---|
| Build command | npm run build |
| Output directory (Vercel) / Publish directory (Netlify) | dist |
.env file in the repository, or search the code for
import.meta.env. to see every name the app reads. Add each one to the host's Environment Variables,
spelled exactly the same. For Supabase these are usually VITE_SUPABASE_URL and
VITE_SUPABASE_ANON_KEY (some projects name the second VITE_SUPABASE_PUBLISHABLE_KEY).
VITE_ reach the browser, and everyone can read them
there. The anon key is made for that. A secret key (Supabase's service_role key, a Stripe secret key,
an OpenAI key) must never get a VITE_ name; it belongs in a Supabase Edge Function or another server
part./dashboard gives 404 on refresh.
public/_redirects with one line:
/* /index.html 200
Vercel: a file vercel.json next to package.json:
{ "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }] }Open the failed deploy on the host and read the build log from the top. The first error is the cause; everything after it is fallout. Match it:
| What the log says | Cause |
|---|---|
Could not resolve "./components/Header" from "src/App.tsx" | 1. Capital letters in a file name |
error TS2322, TS2339, TS2345 and similar | 2. A type check the preview skipped |
Vite requires Node.js version 20.19+ or 22.12+, or Unsupported engine | 3. An old Node version on the host |
npm error ERESOLVE unable to resolve dependency tree | 4. Packages that do not fit together |
No Output Directory named "public" found (Vercel) or Deploy directory 'build' does not exist (Netlify) | 5. Wrong output folder |
vite: command not found | 6. The build tools were not installed |
Header.tsx and
header.tsx as the same file. The host's Linux computers do not, so an import that works on your laptop
finds nothing there.
tsc -b && vite build, TypeScript checks every file first and stops the build on the first
mistake. The builder's preview never ran that check.
null, or a field that does not exist on the data). Do not delete the check to get past it: these are
often the same mistakes that crash the page later.NODE_VERSION (for example 22), or a file .nvmrc with that number. Then deploy
again.npm install --legacy-peer-deps gets the deploy
through and is fine as a stopgap, not as the fix. Also keep one lock file only: a project with both
bun.lockb and package-lock.json lets the host pick a different installer than you
tested with.dist.
dist. If the
app sits in a sub-folder of the repository, set that folder as the Root or Base directory too.devDependencies. If the
host has NODE_ENV=production among its environment variables, the installer skips those, and the build
command finds no Vite.
NODE_ENV from the host's environment variables (the build sets it by
itself), or make sure package.json has a build script and the build command is
npm run build, not a bare vite build in a folder without the packages.This is a checklist from engineering practice, not a study: we have not counted how often each error happens. The messages are the tools' own wording and can differ a little between versions, and the hosts rename their menus from time to time. The settings are the standard ones for React apps built with Vite and Supabase, which is what Lovable and Bolt produce by default. Lovable and Bolt can also publish an app for you on their own address; these steps are for when you want it on your own account and domain.
The build worked and the app stops in the browser instead: missing settings, a wrong base path, or Supabase permissions. A blank page after publishing: six causes and the fix for each. Live but slow on phones? Our demo shop, measured before and after: 14.5 s to 1.4 s.
We fix apps made with Lovable, Bolt, Replit, Cursor and other AI builders, in your own code, and tell you in plain words what was wrong. Fixed prices on Fiverr: one bug from $40, up to five bugs with the app deployed and working live from $150. No fix, no charge. A GitHub invite is enough; we never ask for passwords.
See the gig on Fiverr