Vercel Microfrontends checks for missing configuration
By Steven Van ·
Vercel adds a deployment check that blocks a default microfrontends app from reaching production if its config file is missing.
Vercel Microfrontends now runs a "Microfrontends Config Present" deployment check that blocks a default app's deployment if its microfrontends.json is missing from the build output, which stops broken production routing before it ships. The check appears alongside other Native Deployment Checks such as lint and typecheck, and it is blocking by default for eligible apps (projects enrolled in Vercel Microfrontends and set as the default app in a Microfrontends group), with no opt-in required.
The failure mode this catches: an older branch deployment that predates the Microfrontends config gets manually promoted to production. Once a later deployment includes microfrontends.json again, the check passes. Check behaviour can be adjusted from a project's Build and Deployment Settings. Read the full announcement.