This project was generated using Angular CLI version 20.0.0-next.7, referenced at tools/package.json, by running tools/ng new.

/tools/ng is a symlink to /tools/_run_under_cwd.sh which executes the angular_cli.ng_binary(name = "ng") defined in /tools/BUILD.

A bazel build was then configured alongside the Angular CLI using https://github.com/devversion/rules_angular. This runs exactly the same commands that Angular CLI would, but under Bazel. This shows how a project can be in a "hybrid mode" where some developers (and maybe the CI system) can use Bazel, but others can continue using their familiar tools.

See /angular-ngc for a different example where the Angular tooling is discarded and replaced by a more Bazel-idiomatic build pipeline.

To start a local development server, run:

ng serve

Once the server is running, open your browser and navigate to http://localhost:4200/. The application will automatically reload whenever you modify any of the source files.

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

ng generate component component-name

For a complete list of available schematics (such as components, directives, or pipes), run:

ng generate --help

To build the project run:

ng build

This will compile your project and store the build artifacts in the dist/ directory. By default, the production build optimizes your application for performance and speed.

To execute unit tests with the Karma test runner, use the following command:

ng test

For end-to-end (e2e) testing, run:

ng e2e

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.