Overview - Angular-devtools

sySantosh Yadav

angular-devtoolsWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

angular-devtools

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

angular-devtoolsWorkspace

Average execution time

1m 45s

59 CI pipeline executions

Computation time saved

17m 57s

Cache hit rate

40%

Protect cache integrity with sandboxing

Time to Green

1m 38s

Was 1m 39s, improved by 1%

Succeeded
ci/contributor-guidelines-v2
ac5cab16 feat: add Chrome extension host access flow and Elements-panel select… (#50) * feat: add Chrome extension host access flow and Elements-panel selection sync * test: run vitest without Node's built-in localStorage Node 25+ defines a global localStorage that is undefined without --localstorage-file and hides the jsdom one, so the popup and theme-toggle specs failed on Node 26. Start the test workers with --no-experimental-webstorage for both the package and the app runner. * fix(extension): address review on Elements selection sync - Follow Elements-panel selections only while the Components tab is open, instead of switching tabs on every selection. - Settle a component focus request once the tree is loaded, as the Forms tab does, and drop it when the tab changes, so it never selects a component by surprise later. - Bump the extension version to 0.0.5 for the new host permissions. - Drop the unrelated allowBuilds change from pnpm-workspace.yaml. - Rebuild extension/ui. * docs(privacy): cover hosts granted through Allow access The policy still said no data reaches an external server and that nothing leaves the device. With Allow access, the extension can talk to the devtools server on a LAN host or tunnel the developer grants, so say so, keep it distinct from analytics and telemetry, note that Chrome keeps the grant until it is removed, and bump the last updated date.
by Nicolas Fr...
Succeeded
feat/router-redirect-loops
56a6e047 feat: add Chrome extension host access flow and Elements-panel select… (#50) * feat: add Chrome extension host access flow and Elements-panel selection sync * test: run vitest without Node's built-in localStorage Node 25+ defines a global localStorage that is undefined without --localstorage-file and hides the jsdom one, so the popup and theme-toggle specs failed on Node 26. Start the test workers with --no-experimental-webstorage for both the package and the app runner. * fix(extension): address review on Elements selection sync - Follow Elements-panel selections only while the Components tab is open, instead of switching tabs on every selection. - Settle a component focus request once the tree is loaded, as the Forms tab does, and drop it when the tab changes, so it never selects a component by surprise later. - Bump the extension version to 0.0.5 for the new host permissions. - Drop the unrelated allowBuilds change from pnpm-workspace.yaml. - Rebuild extension/ui. * docs(privacy): cover hosts granted through Allow access The policy still said no data reaches an external server and that nothing leaves the device. With Allow access, the extension can talk to the devtools server on a LAN host or tunnel the developer grants, so say so, keep it distinct from analytics and telemetry, note that Chrome keeps the grant until it is removed, and bump the last updated date.
by Nicolas Fr...
Succeeded
fix/vite-tunnel-auth
8e3567d1 feat: add Chrome extension host access flow and Elements-panel select… (#50) * feat: add Chrome extension host access flow and Elements-panel selection sync * test: run vitest without Node's built-in localStorage Node 25+ defines a global localStorage that is undefined without --localstorage-file and hides the jsdom one, so the popup and theme-toggle specs failed on Node 26. Start the test workers with --no-experimental-webstorage for both the package and the app runner. * fix(extension): address review on Elements selection sync - Follow Elements-panel selections only while the Components tab is open, instead of switching tabs on every selection. - Settle a component focus request once the tree is loaded, as the Forms tab does, and drop it when the tab changes, so it never selects a component by surprise later. - Bump the extension version to 0.0.5 for the new host permissions. - Drop the unrelated allowBuilds change from pnpm-workspace.yaml. - Rebuild extension/ui. * docs(privacy): cover hosts granted through Allow access The policy still said no data reaches an external server and that nothing leaves the device. With Allow access, the extension can talk to the devtools server on a LAN host or tunnel the developer grants, so say so, keep it distinct from analytics and telemetry, note that Chrome keeps the grant until it is removed, and bump the last updated date.
by Nicolas Fr...
Succeeded
main
320c950c feat: add Chrome extension host access flow and Elements-panel select… (#50) * feat: add Chrome extension host access flow and Elements-panel selection sync * test: run vitest without Node's built-in localStorage Node 25+ defines a global localStorage that is undefined without --localstorage-file and hides the jsdom one, so the popup and theme-toggle specs failed on Node 26. Start the test workers with --no-experimental-webstorage for both the package and the app runner. * fix(extension): address review on Elements selection sync - Follow Elements-panel selections only while the Components tab is open, instead of switching tabs on every selection. - Settle a component focus request once the tree is loaded, as the Forms tab does, and drop it when the tab changes, so it never selects a component by surprise later. - Bump the extension version to 0.0.5 for the new host permissions. - Drop the unrelated allowBuilds change from pnpm-workspace.yaml. - Rebuild extension/ui. * docs(privacy): cover hosts granted through Allow access The policy still said no data reaches an external server and that nothing leaves the device. With Allow access, the extension can talk to the devtools server on a LAN host or tunnel the developer grants, so say so, keep it distinct from analytics and telemetry, note that Chrome keeps the grant until it is removed, and bump the last updated date.
by Nicolas Fr...
Succeeded
feature/chrome-extension
cdfa76c0 docs(privacy): cover hosts granted through Allow access The policy still said no data reaches an external server and that nothing leaves the device. With Allow access, the extension can talk to the devtools server on a LAN host or tunnel the developer grants, so say so, keep it distinct from analytics and telemetry, note that Chrome keeps the grant until it is removed, and bump the last updated date.
by Nicolas Fr...
Succeeded
feature/chrome-extension
72fea65e fix(extension): address review on Elements selection sync - Follow Elements-panel selections only while the Components tab is open, instead of switching tabs on every selection. - Settle a component focus request once the tree is loaded, as the Forms tab does, and drop it when the tab changes, so it never selects a component by surprise later. - Bump the extension version to 0.0.5 for the new host permissions. - Drop the unrelated allowBuilds change from pnpm-workspace.yaml. - Rebuild extension/ui.
by Nicolas Fr...