Apps

The repository ships three deployable applications in addition to the npm packages:

App	What it is	Page
adev	The angular.dev documentation site. An Angular SSG application built from this repo and deployed to Firebase.	adev
devtools	The Angular DevTools browser extension (Chrome and Firefox).	devtools
dev-app	A scratch Angular app for ad-hoc framework experimentation. Not deployed; runs only locally.	dev-app

There are also two more peripheral targets that aren't full "apps":

• vscode-ng-language-service/ — the VS Code extension that wraps @angular/language-service. Has its own README and release pipeline; built and published from this repo.
• modules/playground/ and modules/benchmarks/ — runnable demos and benchmark workloads. They aren't deployed but are runnable via pnpm bazel run ….

Build orchestration

graph LR
  subgraph Bazel["pnpm bazel"]
    Adev["//adev:build"] --> AdevDist["adev/dist/<br/>(static site → Firebase)"]
    Devtools["//devtools/projects/shell-browser/src:prodapp"] --> Ext["dist/bin/devtools/.../prodapp<br/>(Chrome/Firefox extension)"]
    DevApp["//dev-app:dev-server"] --> Localhost["localhost:4200<br/>(local dev only)"]
  end

Each target's BUILD.bazel sits next to its source: adev/BUILD.bazel, devtools/projects/shell-browser/src/BUILD.bazel, dev-app/BUILD.bazel.

Why three apps?

adev and devtools are user-facing (the docs site and the extension). dev-app exists so framework engineers have a real Angular app to test changes in without spinning up a separate workspace; the integration tests under integration/ cover the production build/deploy paths.

For a fourth "app" that sits in between, the playground/ and benchmarks/ targets under modules/ are runnable workspaces but are not full applications.