angular-tooling

Run ng generate component features/user-profile or the short form ng g c features/user-profile. Add flags like --skip-tests, --change-detection=OnPush, or --inline-template to customize the generated output.

Run ng build --configuration=production or ng build -c production. The output goes to dist/my-app/browser with hashed filenames, and you can enforce bundle budgets configured in angular.json.

Yes, Angular v20 generates standalone projects and components by default, with app.config.ts and app.routes.ts replacing NgModule-based setup. Functional guards and interceptors are also generated by default.

Run ng test --watch=false --browsers=ChromeHeadless for a single headless run suitable for CI pipelines. Add --code-coverage to generate coverage reports for tools like Codecov.

Create a proxy.conf.json mapping paths like /api to your backend target, then reference it in angular.json under serve options or pass it via ng serve --proxy-config proxy.conf.json.

Oversized bundles usually come from missing lazy-loaded routes, non-tree-shakeable imports, or absent budgets. Use loadChildren for code splitting, import specific RxJS operators, and run ng build -c production --stats-json to analyze the bundle.