SDK Reference
Install the SDK from the public npm registry:
Use the narrowest entry point for each module. This keeps browser targets from importing build-only dependencies and makes runtime assumptions explicit.
The root export is convenient for shared types and simple runtime code. Prefer /rspack only in build configuration and scripts, never in a browser or headless target bundle.
Compatibility
The package declares its supported Node.js and peer-dependency ranges in its published metadata. Install peer packages only for the features you use, and keep all Module Federation packages on the same exact version.
Code should treat optional SDK methods and capability groups as feature-detected additions. A host can reject an operation when its realm, scope, permission, or selected target does not authorize it.