Unable to bust cache of module federation remotes.... #18177
Unanswered
shibisuriya
asked this question in
Q&A
Replies: 1 comment
-
Just use |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Feature request
What is the expected behavior?
I use dynamic import() to load the remoteEntry.js file (called moduleEntry.js in the screen shot)... Dynamic import is caching the remoteEntry.js file... I some how forced my app to load new instances of remoteEntry.js using cache busting... But I have no control over what the remoteEntry.js is further loading... The remoteEntry.js is further loading components code using dynamic import from the dev-server... But I can't bust this cache, so old components are getting loaded...
What is motivation or use case for adding/changing the behavior?
I am trying to build a dev tool that lets me develop components and embed inside a production webapp... So the remote will be running on my machine and the production app will be loaded from a cdn or something... These components that are loaded from the local, I need to support hot reloading inside the production app instead of refreshing the entire webapp...
How should this be implemented in your opinion?
I don't have deep knowledge about webpack internals... A flag to cache bust not only the entry file but also the components that the entry file loads is good...
Are you willing to work on this yourself?
yes
Beta Was this translation helpful? Give feedback.
All reactions