🛠️ Build Logic Hijacked: How a Single Array in vercel.json Silences Your Dashboard

Vercel’s Unused Build Settings Warning

When config overrides sabotage your civic-grade deployments

Let me walk you through a common Vercel warning that’s as sneaky as a ghost project in a county budget. If you’ve ever seen this message:

"Warning: Due to builds existing in your configuration file, the Build and Development Settings defined in your Project Settings will not apply."

Here’s what’s happening: Vercel has detected a builds array in your vercel.json. That array overrides any build settings you may have configured in the dashboard UI—like build commands, output directories, or environment variables. In short, your dashboard settings are ignored.

Why This Happens

Vercel prioritizes vercel.json over dashboard settings. If your config includes a builds array, Vercel assumes you want full control and disables the UI-based logic. This is typical in setups using custom frameworks like Sapper, bespoke Node.js backends, or non-standard build pipelines.

How to Fix or Work Around It

Choose your path based on how much control you want over your build logic.

Goal	Action
Use dashboard settings	Remove the builds array from vercel.json. Let Vercel auto-detect your framework.
Keep full control	Stick with vercel.json, but define all necessary build logic manually.
Hybrid setup	Avoid conflicting definitions. Don’t define builds in both dashboard and vercel.json.

Here’s a minimal vercel.json that avoids the warning:

{
  "version": 2,
  "rewrites": [
    { "source": "/(.*)", "destination": "/api" }
  ]
}

Debugging Tips

• Check your build logs in the Vercel dashboard under Deployments → Build Logs.
• Look for red-highlighted errors or skipped steps.
• Try building locally with npm run build or yarn build to catch issues before deploying.

If you’re wiring civic modules or dashboard endpoints, this warning is like a phantom override—looks harmless, but it can silently sabotage your build logic. Always audit your config like you’d audit a county procurement file: no assumptions, no placeholders, no rot.

Author: Peter M. Mutiti | Investigative Journalist & Civic Technologist

MIT License © 2025 Peter M. Mutiti · View License