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
Charles Lyding e149ebf228 build: update rxjs build version to v7 (#53500) 
The version of rxjs used to build the repository has been updated to v7.
This required only minimal changes to the code. Most of which were type
related only due to more strict types in v7. The behavior in those cases
was left intact. The most common type related change was to handle the
possibility of `undefined` with `toPromise` which was always possible with
v6 but the types did not reflect the runtime behavior. The one change that
was not type related was to provide a parameter value to the `defaultIfEmpty`
operator. It no longer defaults to a value of `null` if no default is provided.
To provide the same behavior the value of `null` is now passed to the operator.

PR Close #53500
2023-12-18 16:25:37 +00: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 build: update rxjs build version to v7 (#53500) 2023-12-18 16:25:37 +00:00
src refactor(devtools): run control flow migration. (#53353) 2023-12-05 17:20:09 -08:00
tools build(devtools): make sure linker runs on fesm2022 bundles (#50086) 2023-05-09 14:41:48 -07:00
.gitignore refactor(devtools): prepare codebase for migration to angular/angular repo 2021-11-21 20:23:18 -05:00
BUILD.bazel refactor(devtools): consolidate devtools global styles into 1 file (#49001) 2023-02-14 20:25:23 +01:00
CONTRIBUTING.md docs: updating the contribution guidline docs with the secure tag (#50618) 2023-06-22 09:41:26 -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
styles.scss feat(devtools): Implement initial DI debugging features in devtools (#51719) 2023-10-10 13:10:50 -07:00
tsconfig.json refactor(devtools): enables typescript strict option (#53340) 2023-12-05 12:42:56 -08: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

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"