The Hidden Cost of Waiting: Build Time as a Productivity Killer
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Swiggy's engineering team reduced build times by up to 80% across multiple repositories through systematic optimization. Key strategies included using tar archives instead of direct file copies to Docker, migrating from npm to Yarn workspaces, parallelizing builds, removing redundant package builds in monorepos, separating SDK
•12m read time• From bytes.swiggy.com
Table of contents
ProblemSteps takenDoing a tar copy of node_modules to Docker instead of a direct copyMigration to yarn and yarn workspacesDoing yarn install in the final dist folder instead of copying from the build.Lerna workspace, removing individual builds of packagesRemoving publish and running publish for SDK on a separate threadParallelizing buildsUsing an alias for build names across environmentsGet Ashoka Chandra Wardhan’s stories in your inboxDeletion of git tags and branchesThe three-legged journeyRepo SEORepo discoveryRepo CheckoutFinal Output 📈📈📈Closing ThoughtsSort: