The post discusses the process of moving JavaScript code into a monorepo at Aha! The author explains the drawbacks of using private npm packages and the need for a monorepo. They describe the steps taken to maintain Git history and choose a tool for the monorepo. After trying out various options, they settle on Turborepo and pnpm workspaces. They highlight the simplicity and frictionless experience provided by Turborepo, which has helped save development time and improve the overall developer experience.
Table of contents
Do we need a monorepo?We need a monorepo — now what?Maintaining Git historyKeeping it simpleNx + pnpmpnpm workspacesTurborepo + pnpmNo new things to learnIt just works!2 Impressions