angular/devtools
Shuaib Hasan Akib f87e9a02b5 refactor(devtools): clean up unused code and modernize component patterns
- Removed unused code and imports
- Migrated to signal-based input() APIs
- Added readonly to Angular-initialized inputs and removed explicit type annotations
- Updated templates to use self-closing tags for consistency
2025-11-17 08:40:15 -08:00
..
cypress refactor(devtools): add clear button to the directive explorer filter (#64407) 2025-10-14 09:28:39 -07:00
docs build: format md files 2025-11-06 10:03:05 -08:00
projects refactor(devtools): clean up unused code and modernize component patterns 2025-11-17 08:40:15 -08:00
src refactor(devtools): increase font weight in the demo app 2025-11-17 08:37:55 -08:00
tools refactor(devtools): remove hard newlines from reviewer note (#64062) 2025-09-25 10:36:41 -04:00
.gitignore refactor(devtools): prepare codebase for migration to angular/angular repo 2021-11-21 20:23:18 -05:00
BUILD.bazel build: move all rule/macro loading into devtools/defaults.bzl (#62627) 2025-07-14 15:47:05 -07:00
cypress.json refactor(devtools): bring the angular devtools directory into the root bazel workspace 2022-01-26 16:35:31 -05:00
README.md build: format md files 2025-11-06 10:03:05 -08:00
tsconfig-test.json refactor(devtools): use signal inputs for split component (#62550) 2025-07-11 10:37:50 -07:00
tsconfig.json build: adopt moduleResolution: "bundler" (#64125) 2025-09-29 14:20:23 -04:00
tslint.json build(devtools): disable the "Rebase PR on target branch" circleci job so that the PR that merges the unrelated history of rangle/angular-devtools can be successfully merged into angular/angular 2022-01-26 16:35:30 -05:00

Angular DevTools

Angular DevTools is a browser DevTools extension for debugging and profiling Angular applications.

Developing Locally

Set up

Follow the instructions below to set up your Angular DevTools development environment. Note that all commands should be executed in the repository root, not devtools/. All file paths are also relative to the repository root.

Debian Linux, MacOS, and Windows via WSL should build successfully. Building natively on Windows without WSL is not supported at the moment.

To set up your development environment, first install the correct version of Node. If you have nvm set up, this can be done with:

nvm install

Second, install pnpm:

npm install -g pnpm

Third, install NPM dependencies:

pnpm install --frozen-lockfile

Now you should be ready to build the DevTools extension.

Dev builds

To run the extension in development mode run:

pnpm devtools:devserver

This would start a development server that you can access on http://localhost:4200. In development, Angular DevTools uses a "development shell." This is different from "chrome shell" in a way, that it runs the user's app in an iframe. DevTools then communicate with the user's app via message passing.

Running End-to-End Tests

Before running end-to-end tests, you need to start the development server using:

pnpm devtools:devserver

You have two options for running cypress, you can use the interactive cypress UI or you can run Cypress in headless mode.

To open Cypress for Angular DevTools in interactive mode, run:

pnpm devtools:e2e:open

To run Cypress tests headless, use:

pnpm devtools:test:e2e

Release builds

You can build the release version of Angular DevTools for either Chrome or Firefox with:

pnpm devtools:build:chrome:release
pnpm devtools:build:firefox:release

Either way, the built extension will be at dist/bin/devtools/projects/shell-browser/src/prodapp.

Installation

For Chrome, you can install the extension from dist/bin/devtools/projects/shell-browser/src/prodapp by following the guide from here.

For Firefox, to load the extension, you can go to the about:debugging page, click the "This Firefox" option and then click the Load Temporary Add-on button. You'll have to select the manifest file in dist/bin/devtools/projects/shell-browser/src/prodapp directly.