revalidate doesn't refresh server chunks without server restart

[rohit1576]

In the example given here - https://github.com/module-federation/module-federation-examples/tree/master/nextjs-ssr

The latest server chunk does not load in host app, if some changes are done in remote app. The same issue is happening both on dev and prod build.

Steps to reproduce:

1. Run pnpm dev, and hit http://localhost:3000/
2. Make changes in checkout/components/exposedTitle.js, on string present at line 14.
3. Refreshing the page will load the latest client chunk with updated content, but on server, still the old content would load. (You can verify this by disabling javascript in browser)
   Error:

Even tried adding content hash in the output.filename in webpack config as mentioned here - https://github.com/module-federation/core/tree/main/packages/node#utilities, but no luck.

[rohit1576]

@ScriptedAlchemy

My use case is to make remotes revalidate on SSR, whats the way to achieve it?

[karanpvyas]

Facing the same issue, currently I'm having to "restart" my production pods to use latest remote after one of the remotes is built and uploaded to cdn
Moreover, my remotes are versioned already. (xx/remoteEntry-.js)

[darshan0919]

I am also facing the similar issue with my codebase, is there a way to fix this?

[s1ddharthgarg]

Facing the same issue, any suggestions to fix this?

[ScriptedAlchemy]

Loop over the require cache, like I do in that utility. But try more aggressive. Delete everything

[karanpvyas]

@ScriptedAlchemy Thanks for the response; Do you mean there might be some issue around require's cache clearing in the revalidate workflow - is that the correct direction to check further here?

(and not at my end inside my document.tsx and other nextjs ssr workflow)

[ScriptedAlchemy]

Yeah most likely