a platform for microfrontends ✦

Ship independently. Compose natively.

Each team publishes TypeScript source. The JIT server compiles it on first request. The browser resolves every fe(scope/name) specifier through import maps at runtime. No shared build pipeline. No version negotiations at deploy time.

◆ MFE teams
fe publish · fe dev · fe new
◆ JIT server
fe serve · compiles on demand
◆ platform config
platform.json · routes + packages
◆ browser runtime
import maps · @fe/runtime · render()
✦ Product engineering
How to scaffold, develop, and publish a MFE independently.
Scaffolding Dev workflow Publishing
❖ Platform engineering
How to operate the JIT server, shell, and manifest.
JIT Server Manifests Rollbacks
◎ Architecture & design
The fe() convention, import map lifecycle, and plugin system.
Convention Import Maps Plugins
➤ Hands-on tutorials
Step-by-step tutorials from hello world to toolkit integration.
Hello World State Sharing Deps