<?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 Commentary of Takao</title><link>https://takao.blog/en/tags/build-tools/</link><description>Recent content in Build-Tools 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/build-tools/index.xml" rel="self" type="application/rss+xml"/><item><title>Monorepo Management with Turborepo: Scaling Development</title><link>https://takao.blog/en/web/monorepo-turborepo/</link><pubDate>Tue, 24 Sep 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/monorepo-turborepo/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Monorepo Management with Turborepo: Scaling Development" /&gt;&lt;h2 id="introduction"&gt;Introduction
&lt;/h2&gt;&lt;p&gt;As JavaScript monorepos grow, build times spiral, CI pipelines saturate, and developer productivity drops. Turborepo, created by Vercel, addresses these challenges with intelligent caching and parallel task execution. Unlike Lerna or Nx, Turborepo focuses on being a task runner rather than a build tool, delegating compilation to tools like esbuild, webpack, and tsc.&lt;/p&gt;
&lt;h2 id="core-architecture--the-cache-system"&gt;Core Architecture — The Cache System
&lt;/h2&gt;&lt;p&gt;Turborepo&amp;rsquo;s cache is its defining feature. Cache keys are computed from file contents, environment variables, and dependency graphs. The cache lives in &lt;code&gt;node_modules/.cache/turbo&lt;/code&gt; as tar.gz archives, and the cache hit/miss lifecycle determines whether a task executes or skips.&lt;/p&gt;</description></item><item><title>Vite Plugin Development: From Zero to Production</title><link>https://takao.blog/en/web/vite-plugin-dev/</link><pubDate>Mon, 05 Feb 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/vite-plugin-dev/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Vite Plugin Development: From Zero to Production" /&gt;&lt;p&gt;Vite&amp;rsquo;s plugin system is one of its most powerful features, allowing developers to extend and customize the build pipeline. Whether you need to transform file types, inject build-time constants, or integrate with other tools, the Vite plugin API gives you full control.&lt;/p&gt;
&lt;h2 id="understanding-vites-plugin-system"&gt;Understanding Vite&amp;rsquo;s Plugin System
&lt;/h2&gt;&lt;p&gt;Vite plugins are objects with hook functions that execute at specific points in the build lifecycle. Plugins operate in three phases: serve (dev server), build (production), and SSR. A basic plugin looks like this:&lt;/p&gt;</description></item></channel></rss>