Skip to content

Latest commit

 

History

History
57 lines (42 loc) · 6.64 KB

platforms.md

File metadata and controls

57 lines (42 loc) · 6.64 KB
title Platforms
description The browsers, devices and app frameworks the devtools inspect today, how each one is checked, and the platforms still planned with their tracking issues.
Where an Angular app can run and still report to the devtools, and which platforms are planned next.

Platforms

The devtools read a running Angular app through its debug API, wherever it renders. A browser page runs the browser overlay. A platform without a DOM gets an overlay of its own that walks its view tree and sends the same reports. For the build tools and servers each setup uses, see Supported setups.

Supported platforms

Platform How it reports How it is checked Set up
Browser The browser overlay, loaded in main.ts or by the Vite plugin CI and the weekly install check, in Chromium Installation
Chrome DevTools The Chrome extension shows the panel for a page that already runs the overlay Package tests of the extension bridge. You build and load the extension from the repository Chrome extension
Firefox DevTools A Firefox build of the extension, for a page that already runs the overlay Package tests of the manifest it writes. CI does not build it, and you load it as a temporary add-on Build for Firefox
Capacitor and Ionic WebViews The browser overlay in the WebView, or overlay-manual in a bundled build. Ionic page stacks show on the Capacitor tab Android emulators and the iOS simulator. Checks on real phones are tracked in #337 Set up Capacitor
NativeScript overlay-nativescript, over a WebSocket The demo in examples/nativescript on the iOS simulator. Android is untested NativeScript
Angular Native overlay-angular-native, over a WebSocket Package tests against a simulated view tree. No automated test runs the demo on a device Angular Native

A platform without a DOM has no picker, no axe pass and no Router, Forms or SSR & HTTP data. The NativeScript and Angular Native pages list what needs a browser.

How a platform shows in the panel

Platform Where its data shows
Browser Every tab, scoped to the page you pick.
Capacitor Every tab, like a browser tab, and the Capacitor tab for plugin calls and Ionic page stacks.
NativeScript The tabs it fills, in the Angular dock or the CLI panel without ?view.
Angular Native The Angular Native view (?view=angular-native), and the panel without ?view.

The hub's NativeScript dock always shows the setup steps and a link to the setup page. The Capacitor dock shows them while no Capacitor app reports, and the Angular Native view says No Angular Native app is connected while none does. list-pages gives each page's platform to agents. See list-pages.

Planned

Plans follow feedback. To ask for a platform, or to move one up, comment on its issue.

Platform or channel What it adds Issue
Other app frameworks One core and an adapter per framework, after the mobile platforms. #307
Chrome Web Store and Edge Add-ons The extension installed from a store, instead of built from the repository. #342

The roadmap lists the rest of the planned work.

Where to next