angular-monorepo-governance

Standard IDs

ID	Severity	What it checks
MFE-001	P1	No enforced module/library-tag boundaries — any app can import any library
MFE-002	P1	Shared library has no clear ownership or cross-team versioning story
MFE-003	P2	No module-federation boundary for apps meant to deploy independently
MFE-004	P2	Cross-cutting concern (auth, theming) reimplemented per app instead of shared

This skill applies once a codebase has split into multiple Angular apps/teams within one workspace (or multiple workspaces). A single-app codebase is fully covered by angular-shared-libraries; this skill governs the boundaries between apps and libraries.

---

Check A — No enforced module/library-tag boundaries (MFE-001)

Detection

Check for Nx's @nx/enforce-module-boundaries ESLint rule (or dependency-cruiser equivalent) configured with tags restricting which libraries a given app/library can import — e.g., a feature library should not import another feature's internals, and a ui library should never import a feature library. Without enforcement, any app can reach into any library's internals, and the intended layered architecture erodes silently over time as deadlines pressure developers to take the shortest import path.

BAD — no boundary enforcement, any import is allowed

// .eslintrc.json — no @nx/enforce-module-boundaries rule configured
{
  "rules": {}
}

// libs/orders/feature/src/lib/order-list.component.ts
import { InvoicePdfRenderer } from '@acme/invoicing/feature/internal'; // reaches into another feature's internals

GOOD — tagged libraries, boundaries enforced by lint rule

{
  "rules": {
    "@nx/enforce-module-boundaries": ["error", {
      "depConstraints": [
        { "sourceTag": "scope:orders", "onlyDependOnLibsWithTags": ["scope:orders", "scope:shared"] },
        { "sourceTag": "type:feature", "onlyDependOnLibsWithTags": ["type:ui", "type:data-access", "type:util"] }
      ]
    }]
  }
}