<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rush on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/rush/</link>
    <description>Recent content in Rush on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/rush/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>JavaScript Monorepo Build Tools in 2026: Nx vs Turborepo vs Rush</title>
      <link>https://www.pistack.xyz/posts/2026-09-08-javascript-monorepo-build-tools-nx-turborepo-rush-comparison/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-08-javascript-monorepo-build-tools-nx-turborepo-rush-comparison/</guid>
      <description>&lt;p&gt;Your CI pipeline just rebuilt every package in the repository — again — even though you changed one file in one library. At 20 packages that is annoying. At 200 packages it burns hours of engineer time and turns every merge into a coin flip on whether the shared cache is warm. Monorepo build tools exist to kill exactly this waste, and in 2026 the JavaScript ecosystem has settled on three serious contenders: &lt;strong&gt;Nx (29,318 stars)&lt;/strong&gt;, &lt;strong&gt;Turborepo (31,069 stars)&lt;/strong&gt;, and &lt;strong&gt;Rush (part of the Microsoft Rush Stack, 6,495 stars)&lt;/strong&gt;. All three are open source, all three are MIT-licensed, and all three were pushed within the last 48 hours — but they approach the problem from surprisingly different angles.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
