Micro Frontends demo beautifully. Two remotes, a shell, a shared header — everything loads, everyone claps.
Then you ship to production, and a different category of problems appears. Problems that never show up in tutorials, never fail in local dev, and never get caught in code review — because they're not code problems, they're architecture problems.
I've spent the last couple of years building and maintaining Angular Micro Frontends (Native Federation, Nx, Angular 17→21) on a large government platform. Here are the 5 mistakes I either made myself or watched teams make — and how to avoid each one.
1. Sharing dependencies without pinning strategy
The default instinct: share everything. Angular, RxJS, your UI library — mark it all as shared and move on.
