Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MFE and PWA #32

Open
Ketec opened this issue Feb 1, 2023 · 0 comments
Open

MFE and PWA #32

Ketec opened this issue Feb 1, 2023 · 0 comments

Comments

@Ketec
Copy link

Ketec commented Feb 1, 2023

PWA / ServiceWorkers for cache and update management are increasingly common with many advantages.

Micro frontends with separately deployable and isolated modules are equally impactful.

But both together become suddenly quite a mess.
You can easily do the shell/host - and cache/update anything changed there - and even serve it as a PWA. But remotes are essentially uncovered.

Dynamic remotes are unknown during build time - their files are unknown and they do not get a unique hash for change detection.
Remotes may load additional dependencies.

Browser caching of files and assets is extremely unreliable. But you can't use service worker for remote projects either - they are only served through shell.

And the second major issue is lack of update notifications - since the worker is not aware that a new version of a remote is available.

How would you approach this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant