Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
angular/devtools
History
AleksanderBodurri 445fbf81fd refactor(devtools): bring the angular devtools directory into the root bazel workspace 
Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm.

Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2022-01-26 16:35:31 -05:00
..
cypress refactor(devtools): run tslint --fix on devtools codebase 2022-01-26 16:35:31 -05:00
docs refactor(devtools): prepare codebase for migration to angular/angular repo 2021-11-21 20:23:18 -05:00
projects refactor(devtools): bring the angular devtools directory into the root bazel workspace 2022-01-26 16:35:31 -05:00
src refactor(devtools): bring the angular devtools directory into the root bazel workspace 2022-01-26 16:35:31 -05:00
tools refactor(devtools): bring the angular devtools directory into the root bazel workspace 2022-01-26 16:35:31 -05:00
.gitignore refactor(devtools): prepare codebase for migration to angular/angular repo 2021-11-21 20:23:18 -05:00
BUILD.bazel refactor(devtools): bring the angular devtools directory into the root bazel workspace 2022-01-26 16:35:31 -05:00
CONTRIBUTING.md refactor(devtools): prepare codebase for migration to angular/angular repo 2021-11-21 20:23:18 -05:00
cypress.json refactor(devtools): bring the angular devtools directory into the root bazel workspace 2022-01-26 16:35:31 -05:00
DEVELOPING.md refactor(devtools): prepare codebase for migration to angular/angular repo 2021-11-21 20:23:18 -05:00
LICENSE refactor(devtools): bring the angular devtools directory into the root bazel workspace 2022-01-26 16:35:31 -05:00
packages.bzl refactor(devtools): bring the angular devtools directory into the root bazel workspace 2022-01-26 16:35:31 -05:00
README.md refactor(devtools): prepare codebase for migration to angular/angular repo 2021-11-21 20:23:18 -05:00
tsconfig.json refactor(devtools): bring the angular devtools directory into the root bazel workspace 2022-01-26 16:35:31 -05:00
tsconfig.spec.json refactor(devtools): prepare codebase for migration to angular/angular repo 2021-11-21 20:23:18 -05: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

README.md

Angular DevTools

Table of content

Introduction

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

You can install the extension from: Chrome Web Store

Inspecting Code

Angular DevTools is a Chrome extension that provides debugging and profiling capabilities for Angular applications. A hard requirement is that the Angular application is running in development mode.

Supported version

Angular DevTools supports Angular v9 and above, with Ivy enabled.

Working on Angular DevTools

Installing and Running locally

To setup your local development environment for Angular DevTools, perform the following steps:

git clone git://github.com/rangle/angular-devtools
cd angular-devtools
yarn
yarn start

Build and Install on Chrome locally

  1. After installation, generate chrome build by running yarn build:chrome
  2. Navigate to chrome://extensions and enable Developer mode.
  3. Choose "Load unpacked extension".
  4. In the dialog, select the directory dist/shell-chrome.

Reporting issues

Please search to make sure your issue is not already been reported. When opening an issue, please follow the issue template provided.

Contributing

General guidelines

If you'd like to help out, please read our Development Guidelines and Contributing Guidelines.

License

MIT