
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Kamil Owczarek | Senior Full-Stack Engineer</title>
      <link>https://whoisarjen.com/blog</link>
      <description>Senior Full-Stack Engineer specializing in high-performance e-commerce, scalable architecture, and performance optimization. TypeScript, React, Next.js, Vue, Nuxt, PostgreSQL, Redis.</description>
      <language>en-us</language>
      <managingEditor>kamilow97@gmail.com (Kamil Owczarek)</managingEditor>
      <webMaster>kamilow97@gmail.com (Kamil Owczarek)</webMaster>
      <lastBuildDate>Mon, 06 Apr 2026 13:00:00 GMT</lastBuildDate>
      <atom:link href="https://whoisarjen.com/tags/bundle-optimization/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://whoisarjen.com/blog/lazy-loading-toast-library-bundle-optimization</guid>
    <title>How We Shaved 22KB Off Our Entry Bundle by Lazy-Loading a Toast Library</title>
    <link>https://whoisarjen.com/blog/lazy-loading-toast-library-bundle-optimization</link>
    <description>vue3-toastify was shipping in the entry chunk of every single page — including those that never show a toast. A dynamic import composable moved it to a separate chunk that loads on first trigger, cutting 22KB from entry.js and 9KB from entry.css.</description>
    <pubDate>Mon, 06 Apr 2026 13:00:00 GMT</pubDate>
    <author>kamilow97@gmail.com (Kamil Owczarek)</author>
    <category>Performance</category><category>Vue</category><category>Nuxt</category><category>Bundle Optimization</category><category>Dynamic Import</category><category>TypeScript</category><category>Web Vitals</category>
  </item>

    </channel>
  </rss>
