nx-workspace-patterns

Set up an Nx workspace by organizing code into apps and libs directories, then configuring nx.json with cacheable operations and target defaults. Use Nx generators to scaffold applications and libraries with consistent settings.

Enforce module boundaries using the @nx/enforce-module-boundaries ESLint rule with tag-based dependency constraints. Assign tags like type:feature or scope:shared to projects, then define which tags each project type may depend on.

Nx affected commands run tasks only on projects impacted by a code change, determined by comparing against a base branch. Running nx affected -t test or build in CI avoids rebuilding unchanged projects, significantly reducing pipeline time.

Yes, Nx supports remote caching through Nx Cloud by setting the tasks runner to nx-cloud with an access token. Self-hosted options also exist, such as S3-based caching via community runners like @nx-aws-cache.

Nx adds overhead that may not suit small single-application repos without shared code. It is designed for monorepos with multiple apps and libraries where dependency graphs, caching, and boundary enforcement provide real value.