nx-workspace-patterns

Create the workspace with the standard apps and libs directory structure, then configure nx.json with your npm scope, cacheable operations, and target defaults. Use Nx generators like @nx/react:lib to scaffold applications and libraries with consistent settings.

Use the @nx/enforce-module-boundaries ESLint rule with depConstraints based on project tags. Assign tags like type:feature or scope:web to each project, then define which tag combinations may depend on each other to prevent invalid imports.

Nx affected commands compare the current branch against a base SHA to identify only changed projects, then run lint, test, and build targets solely on those. Combined with caching, this avoids redundant work and significantly reduces CI duration.

Yes, Nx supports self-hosted remote caching through custom task runners such as @nx-aws-cache/nx-aws-cache, which stores build artifacts in an S3 bucket. Configure it in nx.json under tasksRunnerOptions with your AWS region and bucket.

Nx adds overhead that is not justified for single small applications or repos with no shared code. It is designed for monorepos with multiple apps and libraries where dependency graphs, caching, and boundary enforcement provide real value.