UrgisoftAI-built apps

AI-built apps ยท November 2026

Deploy your Lovable or Bolt app to Vercel or Netlify

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.

The five steps

  1. Get the code onto GitHub. In Lovable, connect the project to your GitHub account from the editor; it creates a repository and keeps it in step with your edits. In Bolt, connect GitHub the same way, or download the project and push it yourself. From here on, the repository is your app: you own it and can move it anywhere.
  2. Import the repository into the host. Vercel: Add New, Project, pick the repository. Netlify: Add new project, Import an existing project, pick the repository. Both read the code and usually guess the settings below. Check them anyway:
    SettingValue for a Vite app
    Build commandnpm run build
    Output directory (Vercel) / Publish directory (Netlify)dist
  3. Copy the app's settings. Open the .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).
    Only names starting with 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.
  4. Add the rule that sends every address to the app. Without it, the home page works and /dashboard gives 404 on refresh.
    Netlify: a file public/_redirects with one line:
    /*    /index.html   200
    Vercel: a file vercel.json next to package.json:
    { "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }] }
  5. Deploy, then point Supabase and your domain at the new address. In Supabase, under Authentication, URL Configuration, set the Site URL to the live address and add it to the Redirect URLs, or login will send people back to the builder's preview. If you sign people in with Google, add the live address in the Google sign-in settings too. Then add your own domain in the host's Domains page and copy the DNS records it shows into your domain registrar; the address can take up to a day to start working, usually far less.

The deploy failed? Six errors and the fix for each

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 saysCause
Could not resolve "./components/Header" from "src/App.tsx"1. Capital letters in a file name
error TS2322, TS2339, TS2345 and similar2. A type check the preview skipped
Vite requires Node.js version 20.19+ or 22.12+, or Unsupported engine3. An old Node version on the host
npm error ERESOLVE unable to resolve dependency tree4. 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 found6. The build tools were not installed
  1. Capital letters in a file name. Windows and Mac treat 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.
    Fix: make the import match the file name letter for letter. If you rename a file only by its capitals, Git may not notice; rename it to a different name, commit, then rename it back.
  2. A type check the preview skipped. If the project's build script is 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.
    Fix: the log gives the file and line; fix what it names (most often a value that can be 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.
  3. An old Node version on the host. Newer versions of Vite and other tools refuse to run on old Node versions, and the host may default to one, or the project may pin one.
    Fix on Vercel: Project Settings, Node.js Version. Fix on Netlify: an environment variable NODE_VERSION (for example 22), or a file .nvmrc with that number. Then deploy again.
  4. Packages that do not fit together. One package asks for a version of React (or another package) that the project does not have. The builder installed it loosely; the host installs it strictly.
    Fix: the log names both packages; move one to a version that fits the other and commit the updated lock file. Setting the install command to 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.
  5. Wrong output folder. The build worked, and the host looked for the result in the wrong place. A Vite app builds into dist.
    Fix: set Output Directory (Vercel) or Publish directory (Netlify) to dist. If the app sits in a sub-folder of the repository, set that folder as the Root or Base directory too.
  6. The build tools were not installed. Vite is listed under devDependencies. If the host has NODE_ENV=production among its environment variables, the installer skips those, and the build command finds no Vite.
    Fix: remove 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 deploy is green, and the page is blank?

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.

Want it deployed for you?

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