You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there possuble way Is there any way to force-refresh mf-manifest.json? The approach using registerRemotes with the force: true option doesn’t work. I’ve often seen recommendations to version mf-manifest.json, but it’s not very clear how the host application is supposed to know which manifest version to load, so that approach doesn’t seem very practical. Most likely I’m missing something in the configuration, but I’ve already tried all the options described in the documentation and the manifest still isn’t being reloaded.
It’s important for me to be able to reload it because the JS chunks of the remote application contain hashes, and with each build the file paths change. In a situation where the user has already loaded the manifest but hasn’t yet loaded the chunks, a subsequent attempt to fetch those chunks will fail because they no longer exist on the server. That’s why I need a way to forcibly re-fetch the manifest when such an error happens — and that behavior seems reasonable to me
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Is there possuble way Is there any way to force-refresh mf-manifest.json? The approach using registerRemotes with the force: true option doesn’t work. I’ve often seen recommendations to version mf-manifest.json, but it’s not very clear how the host application is supposed to know which manifest version to load, so that approach doesn’t seem very practical. Most likely I’m missing something in the configuration, but I’ve already tried all the options described in the documentation and the manifest still isn’t being reloaded.
It’s important for me to be able to reload it because the JS chunks of the remote application contain hashes, and with each build the file paths change. In a situation where the user has already loaded the manifest but hasn’t yet loaded the chunks, a subsequent attempt to fetch those chunks will fail because they no longer exist on the server. That’s why I need a way to forcibly re-fetch the manifest when such an error happens — and that behavior seems reasonable to me
Beta Was this translation helpful? Give feedback.
All reactions