tool

Angular CLI

Angular CLI (`@angular/cli` on npm) is Google's official scaffolding, build, and dev-server tool for Angular, maintained in the angular/angular-cli GitHub repo (MIT license, 27,020 stars). Current release is 22.0.7, published July 15, 2026, tracking Angular 22 after Angular 21 (Nov 2025) made zoneless change detection the default for new projects. Since Angular 17, new apps default to the `application` builder: esbuild handles production bundling while Vite powers the dev server only (HMR, dependency pre-bundling) — the old Webpack-based `browser` builder is now legacy/deprecated but still selectable. It's free and open source, no paid tier. npm shows roughly 4.92M weekly downloads for the week of July 8-14, 2026. Current version/status: 22.0.7 (July 15, 2026). License: MIT. Pricing: Free and open source under MIT; no paid tier for the CLI itself — Nx Cloud, a separate product some teams pair with it, runs a free Hobby plan (50K monthly credits) up to a $19/active-contributor/mo Team plan. Maintained by Google (Angular team).

Also known as: Angular Command Line Interface, ng CLI, Angular CLI tool, Angular CLI commands, Angular CLI utility

🧊Why learn Angular CLI?

Pick Angular CLI straight when you're shipping one Angular app and want Google's own esbuild+Vite pipeline with zero extra config — SSR, prerendering, and HMR just work, and it costs nothing. Don't reach for it bare in a multi-app monorepo with shared libraries fighting CI cache misses — use Nx instead, which wraps the same `@angular-devkit`/esbuild builders as thin executors but adds process-level task caching, and paid Nx Cloud remote caching ($19/contributor/mo Team plan) on top. The CLI's own docs concede the honest weakness: Vite only drives `ng serve`, not `ng build` — production still goes through esbuild alone, so dev and prod bundling paths diverge enough to surface edge-case dependency-resolution bugs late. If you want a leaner, Angular-CLI-free Vite setup, that's Analog, not stock `ng build`. Known weakness: Vite only accelerates the dev server (`ng serve`); production builds (`ng build`) still go through esbuild alone, so dev and prod bundling behavior can diverge on edge-case dependency resolution.