@module-federation/rspack

Coming from Webpack Module Federation, the transition to @module-federation/rspack feels familiar yet unpolished. The core API mirrors the Webpack plugin closely, which helps if you're already familiar with the concepts. However, the documentation often assumes prior knowledge and lacks comprehensive real-world examples beyond basic setups.

Error messages can be cryptic when things go wrong, especially around remote module loading failures or version mismatches. Debugging requires diving into the runtime code more often than I'd like. The package is evolving rapidly, which means breaking changes between minor versions have caught me off guard. GitHub issues get responses, but many remain open with workarounds rather than fixes.

When everything works, the performance benefits of Rspack shine through. Simple host-remote setups are straightforward, but complex scenarios like shared dependency versioning or dynamic remotes require trial and error. The community is growing but Stack Overflow coverage is sparse, so expect to rely heavily on GitHub issues and Discord for help.

The @module-federation/rspack package brings module federation capabilities to Rspack builds, enabling micro-frontend architectures with the speed benefits of Rspack. The core functionality works well once configured, and the performance improvements over Webpack-based solutions are noticeable. However, the developer experience feels rough around the edges compared to more mature tooling.

The TypeScript types are present but often too generic, making it difficult to discover available options through IDE autocomplete. Error messages when misconfiguring remotes or shared dependencies can be cryptic, often requiring deep debugging to understand what went wrong. The documentation exists but lacks the depth needed for non-trivial scenarios—you'll find yourself reading source code or searching for community examples frequently.

Migration from @module-federation/enhanced or native Webpack module federation requires careful attention, as some configuration patterns differ subtly. The getting-started examples are functional but minimal, leaving you to figure out production concerns like error boundaries, loading states, and type sharing on your own.

Getting started with @module-federation/rspack requires patience. The documentation exists but often assumes familiarity with webpack's Module Federation, which helps but doesn't cover Rspack-specific quirks. Setting up your first federated module involves quite a bit of trial and error—expect to spend time debugging configuration issues. The error messages when things go wrong are often cryptic, pointing to internal loader failures rather than your actual misconfiguration.

Once you get past initial setup, the core functionality works reliably for straightforward use cases. Remote module loading and shared dependencies behave as expected when properly configured. However, debugging runtime issues can be challenging since errors may surface as generic "Cannot read property" messages without clear indication that federation is involved.

Community support is growing but limited compared to webpack alternatives. GitHub issues get responses but can take time. Stack Overflow content is sparse, so you'll rely heavily on existing examples and GitHub discussions. The package is actively maintained but feels like it's still maturing—expect to consult the source code occasionally.