Compiling Angular Libraries Properly in a Multi-Framework SDK Monorepo

The Angular SDK's compilation process was incorrectly set, leading to a crash when using the `TraceDirective`. The root cause was that the SDK was compiled with TSC instead of the Angular CLI (`ngc`) under the hood. This difference in compilation resulted in incompatible output files between TSC and ngc, causing the error. To fix this, the team switched from TSC to ngc and implemented a consistent project structure, build process, and tarball format that aligns with the Angular 10 Package Format (APF). The change required modifications to the Angular config, library packager configuration, and default `tsconfig.json`. By adopting the APF, the SDK's contents changed, but this was necessary for first-class support of Angular. The team learned valuable lessons about individualism in a mono-repo, making changes to build processes, and responding to feedback from users.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.