1. Module Federation advanced

    A shell application loads three remote modules at runtime. Two were built against one major version of the UI framework and one against the next. Everything works in the shell's local development setup and breaks in production with errors about invalid hook calls and missing context. What is happening, and how should the platform prevent it?

    3 min answer module-federationsingletonsversioningmicro-frontends
  2. Module Federation advanced

    A shell application loads three remote modules from other teams at runtime through module federation. What happens when one remote is unreachable at load time, and separately when a remote ships a change that breaks the shell's assumptions?

    3 min answer module-federationmicro-frontendsruntime-couplingversioning
  3. Module Federation advanced

    A shell loads six runtime remotes. Four belong to one team of nine engineers who already deploy together, the shared framework singleton forces a coordinated upgrade window twice a year, the composed page ships about 1.9 MB of JavaScript, and the last three incidents were a remote that returned 404. Give the sequence for folding those four into the shell under weekly releases, where state can diverge, the point of no return, and how long it really takes.

    3 min answer module-federationmicro-frontendsconsolidationrollback
  4. Module Federation advanced

    Module federation lets teams share components at runtime rather than through published packages. What does that buy and what does it cost?

    1 min answer module-federationruntime-sharingversioningcoupling
  5. Module Federation advanced

    When do micro frontends solve a real problem, and what do they cost?

    2 min answer micro-frontendsmodule-federationorganisationalruntime