This article explains how to reduce bundle size and improve load speed of large micro‑frontend projects by sharing common dependencies through CDN externalization, using tools such as qiankun, vite‑plugin‑cdn‑import, and Rollup plugins for HTML generation.
This article details a practical implementation of the Wujie micro‑frontend framework across three Vue‑based management systems, covering preparation of the host app, login state handling, layout selection, event bus integration, network request management, UI adjustments, and shared state synchronization, with code snippets and lessons learned.
This article documents several practical problems encountered when using the Wujie micro‑frontend framework—such as editor selection failures, PDF preview white screens, missing Element‑Plus styles, tooltip offsets, custom event loss, and global style pollution—and provides concrete reproduction steps and detailed solutions for each.
This article explains how the WPM (Web Package Manager) was created to enable micro‑frontend resource sharing and hot‑module updates on legacy Webpack 4 projects, detailing the challenges of missing module‑federation support and the custom plugins and loaders that bridge the gap.
GrowingIO’s frontend team transformed its monolithic SaaS product into a micro‑frontend architecture to support on‑premise deployments, detailing the motivations, design principles, code adaptations, integration strategies, and challenges such as dependency conflicts, global variables, and style isolation.
This article examines the micro‑frontend architecture of icestark, analyzing workbench and large monolithic application scenarios, comparing technical options such as SPA/MPA, iframe and shared components, and detailing core concepts, routing, isolation, communication, and micro‑module capabilities to guide practical implementation.
This article explores the challenges of routing in micro‑frontend architectures, explains why correct parent‑child routing is essential, walks through progressively more sophisticated solutions—including shared routes, sandbox isolation, and message‑based synchronization—and finally presents a robust implementation that works across diverse scenarios.
This article explains why sandboxing is essential in micro‑frontend systems, compares single‑instance and multi‑instance scenarios, and provides step‑by‑step implementations of JavaScript and CSS isolation using iframe‑based proxies, PostCSS namespace wrapping, and reusable APIs from the open‑source ConsoleOS project.
This article explains how the ICE team created the AppLoader solution for Alibaba's Creator Platform, evolved it into the open‑source icestark framework, and details its architecture, loading strategies, sandbox isolation, and real‑world business value for large, multi‑team front‑end systems.
After three months of development, Fliggy’s integrated operations console combines micro‑frontend and SDK techniques to unify over ten platforms across four scenarios, streamlining configuration, visual consistency, performance, and user feedback, while sharing lessons on architecture, backend gateway, widget integration, and collaborative open‑source contributions.
This article explains Ant Financial's practical adoption of a standard micro‑frontend architecture, covering the motivations, definition, key technical decisions, implementation details, performance optimizations, and the resulting business and engineering benefits across their cloud platforms.
The article explains how micro‑frontend architecture breaks monolithic front‑ends into independent, composable units, outlines its three core values, details the ten technical challenges it must address, and describes the evolving cloud‑centric development model that reshapes front‑end engineering.
