<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Build Tools on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/build-tools/</link><description>Recent content in Build Tools on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 31 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/build-tools/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 23: Build Tools, Bundlers, and Environment Separation</title><link>https://ai-blog.noorshomelab.dev/react-mastery-2026/chapter-23-build-tools-bundlers-environments/</link><pubDate>Sat, 31 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/react-mastery-2026/chapter-23-build-tools-bundlers-environments/</guid><description>&lt;h2 id="introduction-your-codes-journey-to-the-browser"&gt;Introduction: Your Code&amp;rsquo;s Journey to the Browser&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid React developer! So far, you&amp;rsquo;ve mastered creating components, managing state, handling side effects, and even diving into advanced patterns and performance. But have you ever stopped to wonder how the beautiful JSX you write, the TypeScript you love, or the modern JavaScript features you use actually get understood by browsers? Or how your application knows which API endpoint to talk to when you deploy it to a testing server versus your live production site?&lt;/p&gt;</description></item><item><title>How JavaScript Configuration Files Work: Deep Dive into Internals</title><link>https://ai-blog.noorshomelab.dev/how-it-works/how-javascript-configuration-files-work/</link><pubDate>Tue, 13 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/how-it-works/how-javascript-configuration-files-work/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the intricate world of modern JavaScript and web development, projects are rarely simple one-file scripts. They are complex ecosystems involving multiple languages (JavaScript, TypeScript, JSX, CSS-in-JS), diverse tools (linters, formatters, transpilers, bundlers), and varied environments (development, testing, production). At the heart of orchestrating this complexity lies a collection of seemingly simple text files: configuration files. These files are the silent architects that dictate how your code is written, processed, built, and executed.&lt;/p&gt;</description></item></channel></rss>