mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
`entryComponents` have been deprecated since version 9, because with Ivy they weren't necessary. These changes remove any remaining references. BREAKING CHANGE: * `entryComponents` has been deleted from the `@NgModule` and `@Component` public APIs. Any usages can be removed since they weren't doing anyting. * `ANALYZE_FOR_ENTRY_COMPONENTS` injection token has been deleted. Any references can be removed. PR Close #49484 |
||
|---|---|---|
| .. | ||
| cypress | ||
| docs | ||
| projects | ||
| src | ||
| tools | ||
| .gitignore | ||
| BUILD.bazel | ||
| CONTRIBUTING.md | ||
| cypress.json | ||
| DEVELOPING.md | ||
| packages.bzl | ||
| README.md | ||
| styles.scss | ||
| tsconfig.json | ||
| tsconfig.spec.json | ||
| tslint.json | ||
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.jsonfor Chromemanifest.firefox.jsonfor Firefox
- Build the extension:
yarn devtools:build:chromefor Chromeyarn devtools:build:firefoxfor Firefox
- Find the extension production assets in
dist/bin/devtools/projects/shell-browser/src/prodapprelative 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"