#42 most commonbuildBolt.newCursorv0WindsurfLovable

Build fails on the host because of lint warnings ("Treating warnings as errors")

Treating warnings as errors because process.env.CI = true. Most CI servers set it automatically. / Failed to compile. ESLint: 'x' is assigned a value but never used.

Got a slightly different error? Paste the exact message and get a fix prompt tailored to it.

Paste your error →

What it means

Your hosting service checks code-quality warnings more strictly than your preview does. Small issues like unused variables are being treated as fatal errors during the live build.

How to fix it: paste this prompt into your AI builder

Fix prompt for Lovable, Bolt, Cursor, v0, Windsurf
My deploy fails because lint warnings are treated as errors. Fix the actual warnings listed in the build log (remove unused variables/imports, add missing hook dependencies correctly without causing loops). Do not disable ESLint globally. Only edit the files listed in the log.

If the AI can't fix it: manual steps

  1. As a temporary unblock only, some hosts let you set the build command so CI isn't 'true' (e.g. CI= npm run build), but fixing the warnings is better.

Where this happens

Seen in these AI app builders and editors:

Bolt.newCursorv0WindsurfLovable

Sources

Related build errors

Still stuck? Paste your full error and UnstuckMyVibe will match it and hand you the exact fix prompt.

Fix my error →