# Vercel Microfrontends checks for missing configuration

DevFeed: [Vercel Microfrontends checks for missing configuration](<https://devfeed.tech/articles/vercel-microfrontends-checks-for-missing-configuration-1159.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-microfrontends-checks-for-missing-configuration>)

Author: Kit Foster

Published: 2026-07-08T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [configuration](<https://devfeed.tech/tags/configuration.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [production](<https://devfeed.tech/tags/production.md>), [projects](<https://devfeed.tech/tags/projects.md>), [routing](<https://devfeed.tech/tags/routing.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

Vercel added a blocking Microfrontends Config Present deployment check that prevents the default app from reaching production when microfrontends.json is missing from the build outputs.

## Source excerpt

The Microfrontends Config Present deployment check prevents broken production routing by blocking any default app deployment that is missing its microfrontends.json. This appears alongside other Native Deployment Checks, such as lint and typecheck. The check is blocking by default for eligible apps, with no opt-in required. Eligible apps are projects enrolled in Vercel Microfrontends and designated as the default app in a Microfrontends group. If microfrontends.json is missing from the deployment's build outputs, the check fails and prevents the deployment from reaching production. This can happen when a deployment from an older branch without the Microfrontends config is manually promoted. The check passes on the next deployment once microfrontends.json is included in the build outputs. To adjust check behavior, visit your project's Build and Deployment Settings. Read more