The best way to Architect Your Angular Libraries
summary
Claim: architect Angular libraries with sub-entries so consumers get minimal bundles and teammates get clear module boundaries. Live-coding uses Angular CLI, an app + library workspace, three modules (A/B/C), and webpack-era behavior: adding 100 KB of dummy text only lands in C, but importing commonjs moment.js pulls ~350 KB into bundles and inflates main from about 675 KB to ~201 KB after switching to sub-entries. The implemented sub-entry package.json/index/public_api setup fixes code-splitting and commonjs tree-shaking in practice.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:47The Best Way to Architect Your Angular Libraries
- 9:42Live Coding
- 10:21Angular Library Architecture
- 12:09Generate Multiple Modules
- 26:00Codes Splitting
- 26:29Virtual Pre-Bundle
- 33:17Sub Entries
- 37:23Code Splitting
- 44:23Circular Dependency
- 48:24Best Practices
- 54:10Omniboard
- 56:05Custom Dashboards
- 57:41Share the Code
- 58:33What Is the Benefit To Have Single Library with Three Module Sub Entries Instead of Three Distinct Libraries
- 59:58Suggestions on How To Generate Documentation
- 1:01:20Deep Import
related talks
16mBest Practices
35mHow to Organize an Angular Project
33mArchitectures for huge Angular based Enterprise Applications: npm Packages, Monorepos and Microservices
19mTuning Your Angular Application
31mArchitectures for huge Angular based enterprise applications npm Packages, Monorepos and Micro Apps
01h 13mInternals of the Angular CLI
20mArchitectures for huge Angular based Enterprise Applications...
30mFederated Angular: Micro Frontends with Module Federation
