Module Federation: the Federated Applications Revolution

[@Dadaadad268]

29:53 Do you recommend this kind of structure? (having UI library as separate module)

[@aymanpatel5862]

# Motvation 1. Autonamy 2. Orchestration 3. Share dependencies 4. No UX drawback # Possible soln to cross domain UI components 1. Native ESM - Web perf issue due to preloading. - Only ESM compatible - Different asset path causes reusability of ESM asset path. 2. Single Build - Build performance 3. DLL Plugin - Webpack old legacy - Not just good dev exp. - Does not support different version

[@user-zq8bt6hv9k]

When frontend soydevs rediscover osgi and call it a revolution. I wish elon musk buys jquery and fire all the frontend soydevs in the world

[@abstractalgo]

this could have been two slides and 5mins of talking. terrible explanation with no deep insights into how it works.