Angular Libraries: from zero to Open Source
summary
Explains how Angular libraries must follow the Angular Package Format and notes the CLI (since v6) uses ng-packagr to build APF-compliant bundles for multiple module formats, then publish to npm. Recommends semantic-release plus a commit-message convention to automate semver and releases, and details required hygiene: unit tests, CI/CD, Compodoc-generated documentation, a license choice (MIT/GPL/beerware tradeoffs), code of conduct, and issue/PR templates for maintainability.
AI-written summary · about
chapters (10)
- 0:00Introduction to talk
- 2:25What is open source
- 9:13JavaScript module systems
- 13:07Angular package formats
- 15:16Semantic versioning explained
- 18:49Automating versioning
- 22:03Testing and documentation
- 23:28CI/CD for libraries
- 24:55Project setup tips
- 25:38Q&A and closing
related talks
24mPackages for Angular
30mCreate and publish Angular libs like a Pro
28mCreate & Publish Angular Libs like a PRO
22mConfiguring Angular Libraries with Monorepos
16mLet's plant our Angular Tree
01h 03mThe best way to Architect Your Angular Libraries
33mArchitectures for huge Angular based Enterprise Applications: npm Packages, Monorepos and Microservices
28mPackaging Angular
