RemoteEntry Caching Issue with RSBuild & Module Federation

[basit-qayoom]

Packages I'm using:

{
  "@rsbuild/core": "1.1.0",
  "@rsbuild/plugin-react": "1.0.6",
  "@module-federation/rsbuild-plugin": "0.7.0",
  "@module-federation/enhanced": "0.7.0"
}

---

❓ Problem

I’m using RSBuild with Module Federation in both host and remote React applications.

I have the following setup:

• A shell (host) app that connects to Remote A.
• Remote A itself connects to other remotes, like Remote B and Remote C.

When I run the shell, the remoteEntry.js files from remotes (e.g., A, B, C) are getting cached, even though I'm appending query parameters (?v=${Date.now()}) to the filenames to try and bust the cache.

---

✅ What I Tried

Remote config:

pluginModuleFederation({
  name: 'MFCommon',
  filename: `remoteEntry.js?v=${Date.now()}`,
  exposes: {
    './MfCommon': './src/app/routes/RouteList.tsx',
  },
  shared: {
    react: {
      // Shared settings
    },
  },
});

Host (shell) config:

init({
  remotes: [
    {
      name: 'MFCommon',
      entry: `${process.env.PUBLIC_MF_COMMON_REMOTE_PATH}/mf-manifest.json?v=${Date.now()}`,
    },
  ],
});

---

⚠️ Issue Faced

Even with ?v=${Date.now()} in the URL, the browser still caches the remoteEntry.js files, and the only way I’ve found to reflect the changes is to redeploy the remotes.

But here’s where it becomes more complex:

• Let's say Remote A uses Date.now() for its version and consumes Remote B and Remote C.
• If Remote A is redeployed with a new remoteEntry.js?v=timestamp, it tries to fetch the latest versions of B and C.
• However, B and C weren’t redeployed with new timestamps — so A is still fetching cached versions of their remoteEntry.js.
• This forces me to redeploy B and C as well even if they haven’t changed, just to avoid the cache.

---

❓ Question

• Is this expected behavior with the @module-federation/enhanced plugin and RSBuild?
• Or am I missing something in my setup?
• Is there a recommended way to propagate or synchronize cache-busting across interconnected remotes without redeploying every remote?

This inter-dependency is getting hard to manage across teams.

Any guidance on how to make this setup more scalable and avoid unnecessary redeployments would be really helpful 🙏

---

[alexander-akait]

Please ask this in @module-federation, there is no webpack in your tech stack