Why does my Bolt.new app fail to deploy on Netlify?

Common causes include incorrect build settings, missing environment variables, Node.js version mismatches, or dependency issues. The build command or publish directory is often misconfigured when moving from Bolt to Netlify.

What build settings should I use for Bolt.new on Netlify?

Set Build command to 'npm run build' or 'npm build', and Publish directory to 'dist' for Vite apps or 'build' for React apps. Check your package.json to confirm the correct build script name.

How do I fix 'Module not found' errors on Netlify?

This usually means dependencies weren't installed correctly. Check that your package.json is committed to GitHub, delete and recreate package-lock.json, or set NODE_VERSION environment variable to match your local development version.

Fix Bolt.new Netlify Deploy Failed Errors

1

"Build command failed" or "npm run build exited with error"

The Error: Netlify can't find your build command or it's failing during execution.

The Fix:

Go to Netlify Dashboard → Your Site → Site Settings → Build & Deploy
Check "Build command" - should match your package.json scripts
Common values: npm run build, npm build, or vite build
Check "Publish directory" - usually dist (Vite) or build (React)
Trigger a new deploy after changing settings

Check your package.json:


                "scripts": {

                  "build": "vite build",

                  ...

                }

Result: Build command matches your actual build script.

2

"Module not found" or "Cannot resolve dependency"

The Error: Dependencies weren't installed correctly or package.json wasn't committed.

The Fix:

Verify package.json is in your GitHub repo root
Check that package-lock.json or yarn.lock is committed
Go to Netlify → Deploys → Trigger deploy → Clear cache and retry
If still failing, delete node_modules and package-lock.json locally
Run npm install and commit the fresh lockfile

Pro Tip: Always commit lockfiles to ensure consistent installs between local and production.

3

"Publish directory doesn't exist" or "Site not found"

The Error: The build completed but Netlify can't find the output files.

The Fix:

Check your build output locally: run npm run build
Look for the output folder (usually dist or build)
In Netlify settings, set "Publish directory" to match exactly
Case matters: dist ≠ Dist ≠ DIST
Common folders: dist (Vite), build (React), public (some setups)

Vite apps: Check vite.config.js for build.outDir setting

4

"Environment variable not found" or "process is not defined"

The Error: Your app needs environment variables but Netlify doesn't have them.

The Fix:

Go to Netlify Dashboard → Site Settings → Environment Variables
Add all variables from your local .env file
For Vite apps, variables must start with VITE_
Example: VITE_SUPABASE_URL, not just SUPABASE_URL
Trigger new deploy after adding variables

Critical: Environment variables don't auto-update. You must redeploy after changing them.

5

"Node.js version mismatch" or "Unsupported engine"

The Error: Your code requires a different Node version than Netlify uses by default.

The Fix:

Check your local Node version: node -v
Go to Netlify → Environment Variables
Add variable: NODE_VERSION = 18.17.0 (or your version)
Trigger new deploy

Alternative: Create a .nvmrc file in your repo with just the version number (e.g., 18.17.0)

6

"Page not found" on refresh (SPA routing issue)

The Error: Refreshing a page or visiting a direct URL shows 404. This is a single-page app (SPA) routing issue.

The Fix:

Create a file named _redirects in your public folder
Add this line: /* /index.html 200
Commit and push to trigger redeploy

Alternative: Create netlify.toml in root:


                [[redirects]]

                from = "/*"

                to = "/index.html"

                status = 200

Result: All routes serve index.html, letting your React/Vue router handle the path.

Framework	Build Command	Publish Directory
Vite (Vue/React)	`npm run build`	`dist`
Create React App	`npm run build`	`build`
Next.js	`next build`	`out`
SvelteKit	`npm run build`	`build`
Astro	`npm run build`	`dist`

Bolt.new Deploy
Failed on Netlify?

Deploy Failures

Fix Netlify Deployment Errors

"Build command failed" or "npm run build exited with error"

"Module not found" or "Cannot resolve dependency"

"Publish directory doesn't exist" or "Site not found"

"Environment variable not found" or "process is not defined"

"Node.js version mismatch" or "Unsupported engine"

"Page not found" on refresh (SPA routing issue)

Netlify Build Settings Cheat Sheet

Deployment Checklist

Still Can't Deploy?

Bolt.new Deploy Failed on Netlify?

Deploy Failures

Fix Netlify Deployment Errors

"Build command failed" or "npm run build exited with error"

"Module not found" or "Cannot resolve dependency"

"Publish directory doesn't exist" or "Site not found"

"Environment variable not found" or "process is not defined"

"Node.js version mismatch" or "Unsupported engine"

"Page not found" on refresh (SPA routing issue)

Netlify Build Settings Cheat Sheet

Deployment Checklist

Still Can't Deploy?

Bolt.new Deploy
Failed on Netlify?