angular/devtools
AleksanderBodurri 3a688cb5ec build(devtools): fix issue where esbuild configs were not being set properly in DevTools (#48762)
Previously, a createConfig helper function was created to consolidate common esbuild configurations for DevTools. This function is asynchronous, but when it was used to set the configuration in various esbuild config files, it was used as if it was synchronous.

This commit fixes this issue by wrapping the output of the function in await, so that it propagates the configurations to esbuild correctly.

PR Close #48762
2023-01-18 10:45:13 -08:00
..
cypress refactor(devtools): run tslint --fix on devtools codebase 2022-01-26 16:35:31 -05:00
docs refactor(devtools): remove support for v11 and older versions of Angular (#45883) 2022-05-05 15:28:42 -07:00
projects fix(devtools): Replace material imports and styles (#48420) 2022-12-13 13:22:25 -08:00
src fix(devtools): Replace material imports and styles (#48420) 2022-12-13 13:22:25 -08:00
tools build(devtools): fix issue where esbuild configs were not being set properly in DevTools (#48762) 2023-01-18 10:45:13 -08:00
.gitignore refactor(devtools): prepare codebase for migration to angular/angular repo 2021-11-21 20:23:18 -05:00
BUILD.bazel build: simplify sass consumption of Angular CDK/Material in devtools (#46642) 2022-07-01 10:20:51 -07:00
CONTRIBUTING.md build: clean up references to old master branch (#45856) 2022-05-04 16:23:33 -07: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 feat(devtools): renaming shell-chrome (#44952) 2022-04-12 18:41:37 +00: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 docs: simplify the DevTools readme and add publishing instructions (#45905) 2022-05-09 13:58:06 -07:00
tsconfig.json refactor(compiler-cli): remove enableIvy options (#47346) 2022-09-06 11:33:48 -07: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

Angular DevTools

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

Installing and Running locally

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

git clone git://github.com/angular/angular
cd angular
yarn
yarn run devtools:devserver

Publish Angular DevTools

To publish Angular DevTools to Firefox or Chrome stores:

  1. Update the version of the corresponding manifest file. Currently, Angular DevTools uses different versioning compared to the rest of the packages within the monorepo.
  • manifest.chrome.json for Chrome
  • manifest.firefox.json for Firefox
  1. Build the extension:
  • yarn devtools:build:chrome for Chrome
  • yarn devtools:build:firefox for Firefox
  1. Find the extension production assets in dist/bin/devtools/projects/shell-browser/src/prodapp relative to the root of the Angular monorepo
  2. Zip the files in the directory
  3. Upload them to the corresponding store

Firefox

  1. Go to the Firefox Addons page
  2. For email enter devrel@angular.io
  3. Find the password on Valentine
  4. Setup Google Authenticator with the 2FA QR code. You can find the QR code on Valentine

Chrome Web Store

  1. Go to the extension page
  2. Make sure your email is part of the Google Group we use for publishing the extension
  3. Navigate to "Developer Dashboard"
  4. Enter your account credentials
  5. You should be able to change the publisher to "Angular"