TThankGod Chibugwum Obobo4d ago · 7 min readThe Future of Micro-Frontends: How to Combine Module Federation with Server-Side Rendering (SSR)Client-side Module Federation has a well-known weakness, the browser downloads a shell, then fetches remotes, then renders. Users stare at a blank page, and crawlers may see very little. For content-hactocodes.hashnode.dev
JJayesh SojitraSep 23 · 4 min read 5 Frontend Mistakes I Made Early in My CareerIt's easy to read a month of technical posts and assume the person writing them always knew this stuff. I didn't. Here are five real mistakes from early in my career, and what actually fixed each one.1Tjayesh-sojitra.hashnode.dev
CChloe ZhouMay 16 · 8 min readMigrating MUI in a Single-SPA Microfrontend — What the Official Docs Don't Tell YouThis article is the third in a series. The first two cover individual problems in detail: MUI v4/v5 Style Conflicts in single-spa — A Complete Debug Record and Static CSS Leakage in Microfrontends — W1chloezhou.dev
CChloe ZhouApr 23 · 8 min readStatic CSS Leakage in Microfrontends — Why Shadow DOM Fails and How postcss-prefix-selector Fixes ItThis is a follow-up to MUI v4/v5 Style Conflicts in single-spa — A Complete Debug Record. The previous article covered dynamic style conflicts caused by MUI v4 JSS injecting style tags on mount and ov1chloezhou.dev
CChloe ZhouApr 13 · 8 min readMUI v4/v5 Style Conflicts in single-spa — A Complete Debug RecordArchitecture Background The project uses a single-spa microfrontend architecture. The host application is main-app, which loads child apps via a runScript function in react-app.js — including analyticchloezhou.dev
AAnkit SinghApr 11 · 4 min readHow we stopped fearing deployments by moving to Micro Frontend architectureThe problem we had The situation Multiple teams. One React monolith. Every Thursday deployment was a gamble. Team A's fix would break Team B's feature. Nobody wanted to release anything. This is a verankitsinghmyself.hashnode.dev
LLeela Krishna MohanApr 10 · 15 min readMicro Frontend Architecture Part 2: Implementation Guide and Production PatternsIn Part 1, I broke down when Micro Frontends make sense and when they're architectural overkill. We covered the decision framework, performance trade-offs, and red flags to watch for. Now comes the hakrishna-devlog.hashnode.dev
LLeela Krishna MohanApr 7 · 8 min readMicro Frontend Architecture Part 1: When It Makes Sense and When It Doesn'tYou're staring at a monolithic React codebase that takes 8 minutes to build. Your team of 15 developers keeps stepping on each other's toes with merge conflicts. Every feature deployment requires a fukrishna-devlog.hashnode.dev
SSaurabh GuptaMar 9 · 5 min readFrom Single Repos to Nx: My First Monorepo AdventureA few days back, I got the opportunity to work on a project that used an Nx monorepo setup for frontend development. Until then, most of my experience was with single repositories, where each applicatcodecraft-by-saurabh.hashnode.dev
TThankGod Chibugwum OboboMar 8 · 6 min readMicro-Frontends Explained: How to Implement Module FederationFrontend applications are growing in complexity. As teams scale and codebases expand, a single monolithic frontend becomes just as problematic as a monolithic backend, slow builds, deployment bottleneactocodes.hashnode.dev