How to scale up your angular projects like a pro
summary
NX demonstrably speeds builds and tests by caching and running only the affected command, and the demo shows an e‑commerce repo where changing a product component rebuilds just product and app. The dependency visualization is an actual web UI — the dependency graph highlights affected projects. Workspaces differ: buildable vs workspace libraries and publishable libraries change caching and artifacts. Generators and executors automate scaffolding and migrations, NX Console integrates into editors, and NX supports Angular plus other frameworks and backends.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:15Talk overview
- 2:20What is NX
- 4:50Tooling and testing setup
- 6:15Key components
- 8:18NX libraries and types
- 10:51Code splitting best practices
- 12:59Dependency graph benefits
- 14:30NX for monorepos
- 15:15Live demo
- 17:23NX caching and affected commands
- 23:18Pros and cons of NX
- 25:53NX learning resources
- 27:19Q&A
related talks
22mNx for Angular CLI Users
40mNx - Enter Enterprise Development for Angular
26mNx for Angular Developers
35mNx for Angular CLI Users
09mUsing Nx: Angular CLI Power-ups for Modern Development
22mFine-Tuning Your Angular Workflow with Nx: Beyond the CLI
43mNxify your Angular app
40mDriving Your JavaScript Library Ecosystem With Nx
