mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00

Files

T

History

AleksanderBodurri c7eddc24da refactor(devtools): consolidate devtools global styles into 1 file (#49001 )

Previously the DevTools demo app and browser app had duplicated styles in their respective styles.scss files.

This commit creates a global styles.scss that is imported with sass @use into the demo and browser app styles.scss files. This will prevent any issues where css changes to one are missed in the other. Also reduces duplication of material css theme definitions by consolidating it inone place. The respective styles.scss files for the demo app and browser app continue to exist incase those need environment specific css. For example the browser app requires that height: 100% is set on a document in order to render properly in a browsers devtools tab.

PR Close #49001

2023-02-14 20:25:23 +01: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

refactor(devtools): consolidate devtools global styles into 1 file (#49001 )

2023-02-14 20:25:23 +01:00

src

refactor(devtools): consolidate devtools global styles into 1 file (#49001 )

2023-02-14 20:25:23 +01: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

refactor(devtools): consolidate devtools global styles into 1 file (#49001 )

2023-02-14 20:25:23 +01: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

styles.scss

refactor(devtools): consolidate devtools global styles into 1 file (#49001 )

2023-02-14 20:25:23 +01: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

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:

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

Build the extension:

yarn devtools:build:chrome for Chrome
yarn devtools:build:firefox for Firefox

Find the extension production assets in dist/bin/devtools/projects/shell-browser/src/prodapp relative to the root of the Angular monorepo
Zip the files in the directory
Upload them to the corresponding store

Firefox

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

Chrome Web Store

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