<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Javascript Optimization on No Semicolons</title><link>https://nosemicolons.com/tags/javascript-optimization/</link><description>Recent content in Javascript Optimization on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 28 Apr 2026 10:07:33 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/javascript-optimization/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Compression Technique: How I Reduced Bundle Sizes by 40% Using Generated Optimization Patterns</title><link>https://nosemicolons.com/posts/ai-code-compression-bundle-optimization-patterns/</link><pubDate>Tue, 28 Apr 2026 10:07:33 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-compression-bundle-optimization-patterns/</guid><description>&lt;p>Ever stared at a webpack bundle analyzer visualization and felt like you were looking at a digital tumor? Those sprawling red blocks representing your &amp;ldquo;optimized&amp;rdquo; production build can be pretty humbling. I was in that exact spot three months ago, watching our main bundle clock in at a hefty 2.8MB after gzip compression.&lt;/p>
&lt;p>That&amp;rsquo;s when I decided to experiment with something unconventional: using AI not just to write code, but to systematically analyze and compress it using generated optimization patterns. The results surprised me — a 40% reduction in bundle size with zero functionality loss. Here&amp;rsquo;s how I did it, and more importantly, how you can apply these techniques to your own projects.&lt;/p></description></item></channel></rss>