> For AI agents: the complete documentation index is available at https://mfeflow.github.io/mfeflow/llms.txt, the full documentation bundle is available at https://mfeflow.github.io/mfeflow/llms-full.txt. 0.7.0 ON NPM · MIT # One command. Every remote. Pick only what you need. The React micro-frontend boilerplate that keeps going after day one. A shell and remotes on Module Federation 2.0 and Rsbuild, then typed env, GTM with Consent Mode, OpenTelemetry and 18 more features, added when you need them. `$ pnpm create mfeflow my-platform`copy [Read the docs](/mfeflow/guide/quickstart) TypeScript · Rsbuild 2 · pnpm · Turborepo · oxlint ******~/my-app ```` $ npm create mfeflow@latest my-app ✓ shell + catalog + cart, ready in 5.3 s $ pnpm mfeflow dev shell :4300 catalog :4311 cart :4312 $ pnpm mfeflow doctor ✓ one React · one tracer · one tag manager ```` ADD`mfeflow add env-t3` typed env, shell + remotesBUDGET`shell +32 KB max` each remote +10 KB, in CI - 5.3 s create to a running shell + 2 remotes bench, median of 5, warm pnpm store - +160 ms LCP against the same pages built as one app Lighthouse mobile, median of 10, budget 300 ms - 26 features, each one command away mfeflow add - 19 packages, versioned together MIT, npm provenance FEATURES ## Pick only what you need. Code you own is copied into your project. Logic that needs fixes is installed as a package and upgraded with migrations. Third-party features are declarative and never run code. ### Foundation - [tsconfig](/mfeflow/features/tsconfig) - [lint-oxlint](/mfeflow/features/lint-oxlint) - [testing](/mfeflow/features/testing) - [git-hooks](/mfeflow/features/git-hooks) - [commit-prompt](/mfeflow/features/commit-prompt) - [ci-github](/mfeflow/features/ci-github) - [registry-server](/mfeflow/features/registry-server) ### Data and contracts - [env-t3](/mfeflow/features/env-t3) - [url-factory](/mfeflow/features/url-factory) - [http](/mfeflow/features/http) - [route-factory](/mfeflow/features/route-factory) - [event-bus](/mfeflow/features/event-bus) - [data-react-query](/mfeflow/features/data-react-query) - [forms](/mfeflow/features/forms) ### Observability - [analytics-gtm](/mfeflow/features/analytics-gtm) - [analytics-clarity](/mfeflow/features/analytics-clarity) - [telemetry-otel](/mfeflow/features/telemetry-otel) ### Delivery - [registry-static](/mfeflow/features/registry-static) - [release](/mfeflow/features/release) - [deploy-docker](/mfeflow/features/deploy-docker) - [deploy-cloudflare](/mfeflow/features/deploy-cloudflare) ### UI - [theming](/mfeflow/features/theming) - [i18n](/mfeflow/features/i18n) - [tailwind](/mfeflow/features/tailwind) - [ui-shadcn](/mfeflow/features/ui-shadcn) - [storybook](/mfeflow/features/storybook) `$ pnpm mfeflow add telemetry-otel analytics-gtm` # shows the plan, then applies it atomically (--dry-run for the diff) HOW IT WORKS ## From empty folder to a running platform. 1. 01 ### Create `pnpm create mfeflow my-platform`A shell, the remotes you name and the features you pick, in a pnpm and Turborepo monorepo. 1. 02 ### Add `pnpm mfeflow add event-bus http`Typed events between remotes, a fetch client over typed URLs. One command each. 1. 03 ### Develop `pnpm mfeflow dev`The shell and every remote on their own ports, with a dev registry that follows new remotes. 1. 04 ### Check `pnpm mfeflow doctor && pnpm mfeflow budget`One React, one tracer, one tag manager. Bundle budgets in CI, with fixes it can apply. FOR MANY TEAMS ## Many teams, one platform that holds. The parts that break micro-frontends in year two are checked from day one. - ### Singletons, checked React and other stateful libraries are shared once and checked at build and at run time, so two copies never ship. - ### Budgets in CI The perf job holds LCP to +300 ms, the shell to +32 KB and each remote to +10 KB over the same pages built as one app. - ### Ownership in the repo Each remote has an mfeflow.app.json with its owner, routes and contracts, so check-compat and doctor know who breaks what. - ### Declarative third parties A registry feature can add files, dependencies and namespaced scripts. It cannot run code on install or touch your CI. IN PROGRESS · PHASE 05 ## Roll back by pointer, not by rebuild. Remotes are built once and stored by version. Deploy, promote and roll back will move a pointer in the registry index, on any static host or a small server with percentage rollouts. This is being built now; the docs will say when it ships. - `catalog@2.3.1`stored, immutable - `catalog@2.4.0`stored, immutable - `index.json`prod points at one version ## Start with one command. `$ pnpm create mfeflow my-platform`copy MIT licensed · built in the open [Docs](/mfeflow/guide/quickstart)[GitHub](https://github.com/mfeflow/mfeflow)[npm](https://www.npmjs.com/package/mfeflow)[Changelog](https://github.com/mfeflow/mfeflow/blob/main/packages/cli/CHANGELOG.md)