What problem does it solve? Splitting a large frontend into independently deployable applications while serving them as one cohesive site requires complex routing, asset isolation, and local development orchestration that is difficult to configure manually. ## Core Features & Use Cases - Routing Configuration: Define microfrontends.json with path expressions, asset prefixes, and feature-flag-controlled routing between default and child applications. - 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. - Group Management via CLI: Create, inspect, add to, and delete microfrontends groups using vercel microfrontends commands, including JSON output for automation. - Use Case: A platform team splits a monolithic Next.js app into web, docs, and dashboard projects so each team deploys independently, while users see one unified domain with shared navigation. ## Quick Start Ask the assistant to help you create a microfrontends group and generate a microfrontends.json routing config for your Vercel projects.
