<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vite on cloudmato.com</title><link>https://cloudmato.com/tags/vite/</link><description>Recent content in Vite on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Mon, 15 Jun 2026 22:53:17 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/vite/index.xml" rel="self" type="application/rss+xml"/><item><title>Module Federation with Vite: What Works, What Doesn't</title><link>https://cloudmato.com/posts/module-federation-vite-guide/</link><pubDate>Mon, 15 Jun 2026 22:53:17 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/module-federation-vite-guide/</guid><description>&lt;p&gt;Module Federation is one of those concepts everyone name-drops the moment &amp;ldquo;micro frontends&amp;rdquo; comes up in a meeting. Cool, share code at runtime, deploy teams independently, sounds great. Then someone on the team says &amp;ldquo;we&amp;rsquo;re on Vite, not webpack&amp;rdquo; and the whole conversation gets awkward. So what actually happens when you try to bring Module Federation into a Vite project? Some of it works beautifully. Some of it&amp;hellip; really doesn&amp;rsquo;t, at least not yet.&lt;/p&gt;</description></item><item><title>Vite Explained: Why It Beats Webpack and What's Next</title><link>https://cloudmato.com/posts/vite-vs-webpack-why-vite-is-fast/</link><pubDate>Fri, 05 Jun 2026 14:59:00 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/vite-vs-webpack-why-vite-is-fast/</guid><description>&lt;p&gt;I remember the first time I switched a project from CRA (which uses Webpack under the hood) to Vite. The dev server came up in under a second. I genuinely stared at the terminal for a moment, waiting for something else to happen. Nothing did. That was it — it was ready. That&amp;rsquo;s not a small improvement over Webpack. It&amp;rsquo;s a completely different experience.&lt;/p&gt;
&lt;h2 class="header-anchor-wrapper"&gt;What Is Vite?
&lt;a href="#what-is-vite" class="header-anchor-link"&gt;
&lt;svg
xmlns="http://www.w3.org/2000/svg"
width="1rem" height="1rem" viewBox="0 0 24 24" fill="none"
stroke="currentColor" stroke-width="2" stroke-linecap="round"
stroke-linejoin="round"&gt;
&lt;line x1="4" y1="9" x2="20" y2="9"&gt;&lt;/line&gt;&lt;line x1="4" y1="15" x2="20" y2="15"&gt;&lt;/line&gt;&lt;line x1="10" y1="3" x2="8" y2="21"&gt;&lt;/line&gt;&lt;line x1="16" y1="3" x2="14" y2="21"&gt;&lt;/line&gt;
&lt;/svg&gt;
&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Vite (French for &amp;ldquo;fast&amp;rdquo;, pronounced &amp;ldquo;veet&amp;rdquo;) is a frontend build tool created by Evan You — the same person who built Vue.js [1]. It launched in 2020 and has been growing fast. As of 2025, Vite logs &lt;strong&gt;53 million weekly npm downloads&lt;/strong&gt; against Webpack&amp;rsquo;s 36 million [5]. Its GitHub stars tell the same story: 78,000 vs Webpack&amp;rsquo;s 66,000 [5].&lt;/p&gt;</description></item></channel></rss>