Choose how to load WU.
Use npm to integrate it into your build or import the ESM module from a CDN. Keep the same runtime version for every application in a shell.
wu-framework 4.0.0
npm install wu-framework@4.0.0ESM, CommonJS, UMD, and subpaths for adapters and integrations.
npm package ↗WU CLI 1.2.0
npm install --global @wu-framework/cli@1.2.0Workspace creation, development, compilation, and diagnostics.
npm package ↗Versions and verified examples
This documentation covers Framework 4.0.0 and CLI 1.2.0. References are checked against the code and executable examples for these versions.
All labs and downloads pin WU Framework 4.0.0. Terminal guides use CLI 1.2.0. Review breaking changes before upgrading an existing project.
Read the migration guide Get support
Importing from a CDN
import { wu } from 'https://cdn.jsdelivr.net/npm/wu-framework@4.0.0/dist/wu-framework.esm.js';
await wu.init({ sandbox: 'module', apps: [
{ name: 'catalog', url: '/apps/catalog' },
] });
await wu.mount('catalog', '#catalog-slot');Example runtimes
The homepage, API recipes and Apps in motion bundle the runtime. Composition and Services and RPC use a versioned CDN with a local fallback of the same version. Each composition keeps one shared instance.
Downloadable SSR and MCP examples require Node and their processes. Opening the portal does not start a Node server. Worker/WASI examples execute work in the browser behind a WU contract.
Official repositories
Markdown documentation
Documentation and search are generated from the same chapters. Every page has a Markdown version for reading, contributions, and tools.
- WU Framework 4.0 and CLI 1.2: upgrade and migrate
- Frontend development: what you can build with WU
- Your first microapp
- Microfrontends: when to choose WU Framework
- Adding a second app
- Polyglot architecture
- Microfrontends with React, Angular and WU
- WU vs Module Federation and single-spa
- Preparing production
- How the portal is built
- Running the examples
- A counter between React and Vue
- A sum between two microapps
- A service connected through WU
- An editor that keeps its state
- What is WU
- Configuration and manifests
- Lifecycle and ownership
- Loading, entries, and prefetching
- DOM, CSS, and sandbox
- Events, RPC, and contracts
- Shared state
- Navigation and composition
- Astro, React, Vue, and adapters
- Permissions and trust limits
- Public reference
- Diagnostics and testing
- Hooks, plugins, timeline, and AI
- SSR and hydration
- Composition and permission reference
- Store and synchronization reference
- Events, RPC, and contract reference
- Hooks, plugins, and timeline reference
- Loading, cache, and diagnostic reference
- Rendering and HTTP security reference
- Adapter and binding reference
- AI, context, and workflow reference
- Astro, Next, and helper reference
- Core, subsystems and manifests
- Install and restore .wuapp files
- Remote apps and capability ports
- Compare a shadow version
- Transitions, focus and windows
- Drag and drop across apps
- Evolve contracts without breaking clients
- Supervision, recovery and replay
- Progressive SSR and Trusted Types
- Server and SSR recipes
- Runnable AI actions and MCP
- MCP API: bridge, relay, and tools
- What WU CLI does
- Installation and versions
- Creating a project
- Adding and removing microapps
- Configuration and discovery
- Development and reload
- Per-app dependencies and versions
- Build for production
- Serve a production build
- Doctor: local and remote diagnostics
- HTTP policy and host limits
- CLI internals
- Templates and polyglot composition
- Complete command reference
- Package an app with wu pack
- Browser tests and mock apps
- Contracts, types and translators