{remote_name}/index offline issue

[Abhishrut-Peepultree]

Hi all,

I have implemented "@module-federation/nextjs-mf": "8.1.10" for my micro frontend integrations. Upon making a new version release of one of the micro-frontend remotes, when host tries to fetch the "Remote.js" file, host is unable to find the entry file.

Help or Suggestions would be appreciated!

Thanks in advance.

[ScriptedAlchemy]

refresh the page, does it go away?

[Abhishrut-Peepultree]

Yes, on some devices it used to go away and on some it wouldn't.
It did get resolved eventually, when I upgraded to v8.4.8.
The main issue was I think was the version of the remote file the host pulls from the remote servers. With the addition of the timestamp at the end of remote file in the newer version of Next-MF, host is always able to pull the latest version of remote file. Hence, this issue is not popping up(I assume).

What do you think? Could this the accurate assessment?

Thanks for the reply!

[ScriptedAlchemy]

Close!
The issue was related to hot reloading prod / node
There were 2 issues.

1 i somehow lost part of a function that tracks entrypoint chunks in use and clears them from require cache then re-instantiates them in same order they were seen in
2 our federation runtime has its own remote cache which was not fully releasing stale remotes from memory

Each issue was solved in different releases.

But ultimately something was sticking around in memory that should not have been. However these are usually on the node.js side

If node was fine but browser was borked only. Then it could be skewing during release or a race condition of something in flight but not loaded yet. So it was "there" but not yet

[Abhishrut-Peepultree]

Aah. Got it.
Glad to see that it is fixed now.
Thanks for the clarification.

On a separate note, is there any other release are you working upon that I can contribute to? I would very much like to, if possible. Thanks!

[ScriptedAlchemy]

For next.js?
We actually put it into maintenance mode

#3153

[Abhishrut-Peepultree]

It doesn't necessarily have to be Next.js—if you're working on any other collaborative project, I'd be interested in contributing if that works for you.
Thanks!