From 5089c2aea6310a84c539c84463af0c3fe349dd8c Mon Sep 17 00:00:00 2001 From: Niek Otten Date: Wed, 1 Jul 2026 13:23:17 +0200 Subject: [PATCH] fix(portal-self-service): re-export the full Utrecht package from libs/ui (refs #67) Importing UtrechtComponentsModule pulls every component it exports into the AOT compiler scope, so all must be resolvable through the ui barrel; a partial re-export failed a fresh build with NG3004 (masked locally by the Nx build cache, surfaced by nx serve / a --skip-nx-cache build). Re-export the whole package. Co-Authored-By: Claude Opus 4.8 (1M context) --- libs/ui/src/index.ts | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/libs/ui/src/index.ts b/libs/ui/src/index.ts index 7568b55..c672a0d 100644 --- a/libs/ui/src/index.ts +++ b/libs/ui/src/index.ts @@ -5,13 +5,7 @@ // The Utrecht v3 components are NgModule-based (not standalone), so we re-export the module. // A standalone component consumes them by importing UtrechtComponentsModule in its `imports` // (CLAUDE.md §10 forbids *declaring* NgModules in our code, not consuming a third-party one). -// The component classes are re-exported too so the AOT compiler can resolve the template -// directives (utrecht-article, utrecht-button, …) through this barrel. -export { - UtrechtArticle, - UtrechtButtonAttr, - UtrechtComponentsModule, - UtrechtDocument, - UtrechtHeading1, - UtrechtParagraph, -} from '@utrecht/component-library-angular'; +// Re-export the whole Utrecht package: importing UtrechtComponentsModule pulls every component it +// exports into the compiler's scope, so the AOT build needs all of them resolvable through this +// barrel (a partial re-export fails with NG3004 for the first unused component). +export * from '@utrecht/component-library-angular';