From Many Repos to One: An Honest Nx Monorepo Migration Retrospective

Sat, 21 Feb 2026 00:00:00 -0500

Migrating a standalone Angular app to Nx is a one-liner: npx nx@latest init. Migrating many Angular repos to an integrated monorepo is not. We consolidated several large enterprise Angular apps and libraries into a single Nx monorepo in late 2023. Here’s what that actually looked like.

Problem Statement Link to heading

To share components across multiple frontend surfaces (a main web app, a Microsoft Office add-in, and a mobile app), we maintained multiple Angular libraries. Every time we needed to change a shared component, the workflow looked like this:

Nx Angular Component Generation Schematic: Path Does Not Exist

Sun, 06 Oct 2024 15:48:48 -0500

A few years back, I successfully migrated several Angular libraries and applications from individual projects to a monorepo using Nx. Nx is a great tool for managing multiple projects and libraries in a single repository.

Nx provides many schematics to generate code and migrate existing code. One of the most common tasks is generating a new Angular component. However, I encountered an issue where the schematic was unable to resolve the path where it was supposed to generate the code.

Nx on bradleycarey.com

From Many Repos to One: An Honest Nx Monorepo Migration Retrospective

Problem Statement Link to heading

Nx Angular Component Generation Schematic: Path Does Not Exist