Kam d6d51a0ef8 test(devtools): run the orphaned app component spec ...

`app.component.spec.ts` has been in the tree since the initial DevTools commit
in 2020, but no revision of `shell-browser/src/app/BUILD.bazel` has ever listed
it, and that file has no globs. Two of the three specs in the directory are
wired up; this one has never run.

It could not run as written. The setup declared `AppComponent` and imported
`RouterModule.forRoot([])`, neither of which applies now that the component is
standalone and injects `MessageBus` and `DEEP_LINK_INSTANCE_ID`.

It now stubs the `chrome.devtools` surface that `ngOnInit` reads and covers
both lifecycle hooks: the listeners registered on init, the two performance
track emits, the three guards on the deep link listener, and the listeners
removed on destroy.

Follow-up to #70570, which fixed the same problem in ng-devtools-backend.

2026-09-09 16:11:01 +02:00

..

src

test(devtools): run the orphaned app component spec

2026-09-09 16:11:01 +02:00

BUILD.bazel

feat(devtools): renaming shell-chrome (#44952)

2022-04-12 18:41:37 +00:00

set-version.js

refactor: update license text to point to angular.dev (#57901)

2024-09-24 15:33:00 +02:00

tslint.json

feat(devtools): renaming shell-chrome (#44952)

2022-04-12 18:41:37 +00:00