Microfrontends config check prevents missing configuration deployments
Vercel now automatically checks for the presence of microfrontends.json during deployment and blocks any default app deployment that is missing this configuration file, helping prevent broken production routing. The check is enabled by default for eligible Microfrontends projects and can be adjusted in project build and deployment settings.
The Microfrontends Config Present prevents broken production routing by blocking any default app deployment that is missing its . This appears alongside other , such as lint and typecheck.
deployment checkNative Deployment Checksmicrofrontends.json
The check is blocking by default for eligible apps, with no opt-in required. Eligible apps are projects enrolled in and designated as the default app in a Microfrontends group. If is missing from the deployment's build outputs, the check fails and prevents the deployment from reaching production. Vercel Microfrontendsmicrofrontends.json
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 is included in the build outputs. microfrontends.json
To adjust check behavior, visit your project's .Build and Deployment Settings
Source: original entry ↗