Reduce Expo Monorepo CI Build Time

<blockquote> <p><em>Originally published on <a href="https://ajeetchaulagain.com/blog/turborepo-monorepo-ci/" rel="noopener noreferrer">ajeetchaulagain.com</a> on May 13,

<blockquote> <p><em>Originally published on <a href="https://dxcore.dev/blog/six-reasons-ci-got-slower" rel="noopener noreferrer">dxcore.dev</a>.</em></p> </blockquote> <p>I've

<p>Build times, especially in enterprise software projects, are often an overlooked bottleneck that leads to significant inefficiencies. While working on a production ERP,

<p>We moved our Nx monorepo from CircleCI to GitHub Actions on self-hosted AWS runners, tightened caching, and brought the full CI run from ~33 minutes down to ~15 minutes while

<p>With just one migration, we reduced the execution time of yarn install on our CI from ~110s to ~25s. While also removing legacy patching with postinstall and by also keeping

<p>You push a one line fix and wait twelve minutes for CI to tell you it passed. Multiply that by every push, every developer, every day, and the pipeline is quietly the slowest

<p>Every few years, the frontend community rallies around a faster build tool.<br /> Grunt gave way to Webpack. Webpack gave way to Parcel, then Rollup, then Vite. Each one