What problem does it solve? Splitting a large frontend application into independently deployable units that render as one cohesive app is complex, requiring routing configuration, asset isolation, local development proxies, and cross-team deployment coordination on Vercel. ## Core Features & Use Cases - Routing Configuration: Define microfrontends.json with default and child applications, path expressions, asset prefixes, and flag-controlled routing via 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. - Group Management: Use the vercel microfrontends CLI to create, inspect, add to, and delete microfrontends groups, plus configure fallback environments and observability routing. - 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. ## Quick Start Ask the assistant to set up a microfrontends group and generate a microfrontends.json routing /docs paths to a separate docs project.
