NODE: revalidate() doesn't refresh module when a file has been changed and remoteEntry.js is the same. about universe HOT 6 CLOSED

I came here to raise an issue but I'm glad I found this one already here :)
I can confirm @ScriptedAlchemy's suggestion (to use [contenthash]) works perfectly fine, as it slightly changes the remoteEntry.js file to point to the new hashed chunk, causing the revalidate to detect the changes. 🎉

I will submit a PR to include this detail in the revalidate documentation on https://www.npmjs.com/package/@module-federation/node.

from universe.

Had exactly the same issue. With nextJs, I solved this problem by prepending all of our SSR remoteEntry.js files with a timestamp, for each federated module. Physically in the file, and not with webpack. I achieved this by running a node script on the pipeline after the nextjs build. That was the only way for us to get revalidate working. This is similar to what @ScriptedAlchemy suggests above, but since I'm not sure how to update the plugin without understanding the MF internal code, this was the approach I opted for.

@beratbayram this approach might help you ^^^

edit: nodeJs pipeline script that fixed it for me:

const fs = require('fs');

const filePath = process.argv[2];
const timestamp = Date.now();
const content = `//Timestamp: ${timestamp}\n`;

fs.readFile(filePath, 'utf8', (err, data) => {
    if (err) {
        console.error(`Error reading file: ${err}`);
        return;
    }

    const updatedContent = content + data;

    fs.writeFile(filePath, updatedContent, err => {
        if (err) {
            console.error(`Error writing file: ${err}`);
            return;
        }

Docker:

RUN node update-timestamp.js /app/dist/apps/${APP_NAME}/.next/static/ssr/remoteEntry.js

from universe.

this is a little hacky, but absolutely plausible workaround.

Im likely a week or two away from releasing the v7 plugin interation, and ill ensure theres a solid hashing/busting solution cooked directly into the webpack runtime. in v7 i have my own runtime modules so we can easily write something like this into the remote without patching the asset after the fact (one way i did it before was more or less a webpack plugin equivalent of the code you have demoed)

if youre open to testing out the new major release, its on npm under the "next" tag - this is a major rewrite with almost all the code thrown out and rebuilt. getting some feedback ahead of making v7 the stable release would be helpful as its a large change.

most of the requests im holding to implement in v7 - one unknown is the backward compatibility or interop between 6 and 7.

from universe.

remote hashing should work though. Since all chunks are content hashed, so any change to a module = new chunk hash = detectable change to remote.

Are you using [contenthash] on your chunks?

the other option here is i can adjust the plugin slightly and add some runtime module / comment to the remote container that basically acts like a timestamp, every deploy would have a new hash then, always, even if no change exists

from universe.

I should add that with my SSR-less workaround below there is no problem anymore. In root it still requires a manual page refresh but it is clean and errorless.

#1102 (comment)

from universe.

Stale issue message

from universe.