Tooling for Angulars
Angular tooling is the set of commands and build features around the framework. The Angular CLI creates projects, generates code, serves, tests and builds the app, while rendering options such as client-side rendering, server-side rendering and prerendering decide how pages reach the browser, affecting speed and search visibility.
Stage: Production Angular · Part of the Angular roadmap · Last reviewed 19 November 2026
What to learn in Tooling
- Generate components and services with ng generate
- Create a production build and read its output sizes
- Configure environments and build options in angular.json
- Explain the differences between CSR, SSR and prerendering
- Enable hydration so server-rendered pages become interactive without flicker
Tooling interview questions
What is server-side rendering in Angular and why use it?
SSR runs the app on a server to produce full HTML for each request, then the browser hydrates it into the live app. Pages show content sooner and crawlers see real content, helping first paint and SEO. The cost is a server to run and care with browser-only APIs.
What does ng build do differently from ng serve?
ng serve runs a development server with live reload and unoptimised bundles for fast feedback. ng build compiles ahead of time and, with production configuration, minifies, tree-shakes and hashes files, writing optimised static output to the dist folder for deployment.
Where Tooling fits in the Angular roadmap
Tooling belongs to the Production Angular stage (advanced level), which takes about 18 hours. Quality and rendering.
Other units in this stage
Back to the full Angular roadmap