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
Kristiyan Kostadinov 29039fcdbc feat(core): support TypeScript 4.7 (#45749) 
Adds support for TypeScript 4.7. Changes include:
* Bumping the TS version as well as some Bazel dependencies to include https://github.com/bazelbuild/rules_nodejs/pull/3420.
* Adding a backwards-compatibility layer for calls to `updateTypeParameterDeclaration`.
* Making `LView` generic in order to make it easier to type the context based on the usage. Currently the context can be 4 different types which coupled with stricter type checking would required a lot of extra casting all over `core`.
* Fixing a bunch of miscellaneous type errors.
* Removing assertions of `ReferenceEntry.isDefinition` in a few of the language service tests. The field isn't returned by TS anymore and we weren't using it for anything.
* Resolving in error in the language service that was caused by TS attempting to parse HTML files when we try to open them. Previous TS was silently setting them as `ScriptKind.Unknown` and ignoring the errors, but now it throws. I've worked around it by setting them as `ScriptKind.JSX`.

PR Close #45749
2022-04-29 12:19:45 -04:00
..
cypress refactor(devtools): run tslint --fix on devtools codebase 2022-01-26 16:35:31 -05:00
docs docs(devtools): updating firefox documentation (#44952) 2022-04-12 18:41:37 +00:00
projects feat(core): support TypeScript 4.7 (#45749) 2022-04-29 12:19:45 -04:00
src build: replace bazel devserver with shared dev-infra implementation (#45452) 2022-03-28 09:23:28 -07:00
tools build: replace bazel devserver with shared dev-infra implementation (#45452) 2022-03-28 09:23:28 -07:00
.gitignore refactor(devtools): prepare codebase for migration to angular/angular repo 2021-11-21 20:23:18 -05:00
BUILD.bazel build: migrate more usages from @bazel/typescript to @bazel/concatjs (#45431) 2022-03-25 12:18:34 -07:00
CONTRIBUTING.md docs: adjust contributing, developing and overview markdown files (#45464) 2022-03-29 09:22:50 -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 feat(devtools): renaming shell-chrome (#44952) 2022-04-12 18:41:37 +00: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/angular/angular
cd angular
yarn
yarn run devtools:devserver

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-browser.

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