<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Micro-Frontends on Commentary of Takao</title><link>https://takao.blog/en/tags/micro-frontends/</link><description>Recent content in Micro-Frontends on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/micro-frontends/index.xml" rel="self" type="application/rss+xml"/><item><title>JavaScript Module Federation: Micro-Frontends in Practice</title><link>https://takao.blog/en/web/module-federation/</link><pubDate>Tue, 09 Jul 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/module-federation/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post JavaScript Module Federation: Micro-Frontends in Practice" /&gt;&lt;h2 id="introduction"&gt;Introduction
&lt;/h2&gt;&lt;p&gt;Module Federation, introduced in Webpack 5, provides a runtime integration mechanism for building micro-frontend architectures. Unlike build-time integration approaches, it enables independently deployed applications to share code at runtime, facilitating team autonomy and incremental migration without coordinated releases.&lt;/p&gt;
&lt;p&gt;At its core, Module Federation allows a JavaScript application to dynamically load code from another application at runtime. Each participating application exposes a &lt;code&gt;remoteEntry.js&lt;/code&gt; file that serves as the entry point. When a host application needs a component from a remote, it fetches the &lt;code&gt;remoteEntry.js&lt;/code&gt; at runtime and resolves the required module on demand.&lt;/p&gt;</description></item></channel></rss>