What problem does it solve? Splitting a large frontend into independently deployable applications that render as one cohesive app requires coordinating routing, asset prefixes, local development proxies, and cross-app navigation across multiple Vercel projects. ## Core Features & Use Cases - Routing Configuration: Define path-based routing between a default app and child apps via microfrontends.json, including flag-controlled routing with Next.js middleware. - Local Development Proxy: Run only the microfrontend you are working on while the proxy routes other requests to production fallbacks, with Turborepo and polyrepo support. - CLI Group Management: Create, inspect, and delete microfrontends groups and add or remove projects using the vercel microfrontends CLI. - Use Case: A team splits a monolithic Next.js app into a marketing site and a docs app, configures /docs/:path* routing in microfrontends.json, and develops locally against production fallbacks through the proxy on port 3024. ## Quick Start Ask the assistant to set up a microfrontends group and generate a microfrontends.json routing configuration for your Vercel projects.
