rsbuild moduleFederation.options vs. import { ModuleFederationPlugin } from '@module-federation/enhanced/rspack';

[hverlin]

Hi, I would like to know if rsbuild moduleFederation.options is eventually going to be the same as using @module-federation/enhanced/rspack?

Currently, I have noticed that there are two guides:

• the quick-start guide with @module-federation/enhanced/rspack https://module-federation.io/guide/start/quick-start.html#3-exporting-modules-by-the-producer
• the basic CRA guide with rsbuild moduleFederation.options: https://module-federation.io/practice/frameworks/react/index.html

On the module federation options page in rsbuild (https://rsbuild.dev/config/module-federation/options), it says:

When using module federation, it is recommended that you use the moduleFederation.options option provided by Rsbuild. This option will automatically adjust some related configurations to ensure that the module federation application can run correctly.
When you set the moduleFederation.options option, Rsbuild will take the following actions:

• Automatically register the ModuleFederationPlugin plugin, and pass the value of options to the plugin.
• Set the default value of Rspack's output.publicPath configuration to 'auto'.
• Turn off the split-by-experience rules in Rsbuild's performance.chunkSplit as it may conflict with shared modules, refer to #3161.
• Turn off the splitChunks rule of remote entry.

However, the quick start guide (https://module-federation.io/guide/start/quick-start.html#4-starting-the-producer) does not do any of these. Are these steps not required when using @module-federation/enhanced/rspack?

CC @chenjiahan in case you know (not really sure if this question should be in rsbuild repo or here)

(I have also noticed that https://rsbuild.dev/config/module-federation/options is way faster than @module-federation/enhanced/rspack. In the basic examples, updating the provider takes 0.01s vs. 0.80s with the enhanced plugin. For larger app, it's much slower (some ms for rsbuild module federation options vs. 2-3s for the enhanced plugin)

[chenjiahan]

Hi, there is a comparison in the Rsbuild documentation, you can refer to:

https://rsbuild.dev/guide/advanced/module-federation#how-to-use

[ScriptedAlchemy]

2 seconds startup is probably entirely typescript sync related. Since TS is slow already + we sync it into the other apps.

dts: false can also disable them from enhanced, if you want some features and not others.

[hverlin]

Thank you for the answers. I will try it and report back.

Regarding output.uniqueName, it seems to be needed for HMR (found #2210 (reply in thread), so I can do PR to clarify both guides rsbuild and module-federation quick start?

[ScriptedAlchemy]

By all means send as much PR as you like to docs

[joshuapetryk]

Hey - unsure if this is the appropriate thread, but I was trying to follow the quickstart at https://module-federation.io/guide/start/quick-start.html#1-initializing-the-project

but it doesn't seem to work with rspack@latest?
I created a brand new project with pnpm create rsbuild@latest with react and typescript.

for example my defineConfig is sourced from import { defineConfig } from "@rspack/cli"; whereas the quick start has import { defineConfig } from '@rsbuild/core'; however my package.json does not import anything starting with @rsbuild.

therefore my defineConfig looks completely different and does not contain type defs for things like server or tools.

What am I missing here? is this guide no longer applicable?

[chenjiahan]

Rspack CLI and Rsbuild are different tools. you can run 'pnpm create rsbuild@latest' again to create an Rsbuild project