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 the host and remote apps (React or NextJS - based).
When running the shell (host), the remoteEntry.js from the remote application is getting cached aggressively, even though I’m appending a query param to bust the cache.

✅ What I Tried

From remote config:

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

From shell (host) config:

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

⚠️ Issue Faced

Even though remoteEntry.js has a dynamic query parameter (v=${Date.now()}), the file is still cached by the browser. The only way the new version is picked up is if I redeploy the remote application.

In my case:
• Remote A internally calls Remote B and C.
• To avoid caching, if I redeploy Remote A, I also need to redeploy B and C.
• This becomes unmanageable across teams and environments.

⸻

🔍 Question

How can I effectively bust the cache for remoteEntry.js without requiring redeployment of all related remotes (B, C) when Remote A is deployed?

Is there a recommended pattern or setting in @module-federation/enhanced or RSBuild that allows for better cache busting—perhaps using hashed filenames or content-based versioning?

Any help or best practice would be appreciated 🙏