From 74e1b0fca94862fdad2836b3834287ce2b446ff9 Mon Sep 17 00:00:00 2001 From: erKam Date: Sat, 7 Nov 2026 13:08:23 +0000 Subject: [PATCH 1/2] fix(docs): say why signal history is sampled before Angular 20 Installation said signal history uses samples under webpack on Angular 17 to 19, but before 20.0 the write hook can't say which signal was written, so the overlay never installs it on any builder. The live graph needs 20.1 anyway. The setup table drops the claim, and the Signals page gives both reasons. --- .../src/content/getting-started/installation.md | 16 ++++++++-------- apps/docs/src/content/inspectors/signals.md | 2 +- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/apps/docs/src/content/getting-started/installation.md b/apps/docs/src/content/getting-started/installation.md index 34866159..cfe8f758 100644 --- a/apps/docs/src/content/getting-started/installation.md +++ b/apps/docs/src/content/getting-started/installation.md @@ -64,14 +64,14 @@ On Angular 12 to 19 the overlay degrades as the table above shows: ### Setup on Angular 12 to 19 -| Setup | Angular 12 to 16 | Angular 17 to 19 | -| ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | -| Overlay import in `main.ts` | Works with the webpack-based `@angular-devkit/build-angular:browser` builder. Signal history uses samples, since `@angular/core/primitives/signals` exists from 17.0. | Works with `browser` and `application`. Under webpack, signal history uses samples. | -| Vite plugin (Analog) | Works. The plugin points `@angular/core/primitives/signals` at a stub before 17.0. | Works. | -| `initPangularHub()` in an Express server | Works when the server runs on Node.js 22.12 or later. On an older Node.js the hub logs why and turns itself off. To keep the devtools there, run the standalone CLI on Node.js 22.12 or later beside it instead. | Works. | -| Standalone CLI next to `ng serve` | Works. Run `npx pangular dev` with Node.js 22.12 or later, and the app's own CLI with the Node.js version it supports. | Works. | -| Chrome extension | Works on top of any of the setups above. | Works. | -| `@pangular-inspector/devtools/http` | Not available. It imports `REQUEST` and `provideEnvironmentInitializer`, so the build fails. Leave it out; the HTTP timeline and fault rules need it. | Not available before 19.0, for the same reason. | +| Setup | Angular 12 to 16 | Angular 17 to 19 | +| ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| Overlay import in `main.ts` | Works with the webpack-based `@angular-devkit/build-angular:browser` builder. | Works with `browser` and `application`. | +| Vite plugin (Analog) | Works. The plugin points `@angular/core/primitives/signals` at a stub before 17.0. | Works. | +| `initPangularHub()` in an Express server | Works when the server runs on Node.js 22.12 or later. On an older Node.js the hub logs why and turns itself off. To keep the devtools there, run the standalone CLI on Node.js 22.12 or later beside it instead. | Works. | +| Standalone CLI next to `ng serve` | Works. Run `npx pangular dev` with Node.js 22.12 or later, and the app's own CLI with the Node.js version it supports. | Works. | +| Chrome extension | Works on top of any of the setups above. | Works. | +| `@pangular-inspector/devtools/http` | Not available. It imports `REQUEST` and `provideEnvironmentInitializer`, so the build fails. Leave it out; the HTTP timeline and fault rules need it. | Not available before 19.0, for the same reason. | With the webpack-based `browser` builder, use the standalone CLI next to `ng serve`, as in [Client-only Angular CLI app](#client-only-angular-cli-app), or the Express hub for an SSR app. diff --git a/apps/docs/src/content/inspectors/signals.md b/apps/docs/src/content/inspectors/signals.md index 64f3a14a..95addb18 100644 --- a/apps/docs/src/content/inspectors/signals.md +++ b/apps/docs/src/content/inspectors/signals.md @@ -162,7 +162,7 @@ Angular doesn't send a value for `linkedSignal` nodes. The overlay takes it from ### Exact and sampled values -Exact **set** entries come from a hook on signal writes, which the overlay loads from `@angular/core/primitives/signals`. A webpack build (the `browser` builder) leaves that import to run time, where it fails, so there every entry is **sampled**. The overlay matches a write to a node by its name, kind, version and value. It samples everything else each time it reads the page, as **sampled** entries. +Exact **set** entries come from a hook on signal writes, which the overlay loads from `@angular/core/primitives/signals`. Before Angular 20.0 the hook doesn't say which signal was written, so the overlay doesn't install it. A webpack build (the `browser` builder) leaves that import to run time, where it fails. In both cases every entry is **sampled**. The overlay matches a write to a node by its name, kind, version and value. It samples everything else each time it reads the page, as **sampled** entries. In a development build, the Angular compiler names most signals for you. It adds a `debugName` to `signal()`, `computed()`, `linkedSignal()`, `input()`, `model()`, queries, `effect()`, `resource()` and `httpResource()` when the call initializes a class field, a `this.name =` assignment or a variable. The name is the field or variable name. From 6000bf4131ee22c865021bd1f4894d22b245823a Mon Sep 17 00:00:00 2001 From: erKam Date: Sat, 7 Nov 2026 13:14:20 +0000 Subject: [PATCH 2/2] fix(docs): tie signal history to the live graph's Angular version Value history comes with the live graph, which needs Angular 20.1, so there is none before it. The sampling paragraph no longer claims anything about older versions, where the hook may or may not install. --- apps/docs/src/content/inspectors/signals.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/src/content/inspectors/signals.md b/apps/docs/src/content/inspectors/signals.md index 95addb18..4e398fa5 100644 --- a/apps/docs/src/content/inspectors/signals.md +++ b/apps/docs/src/content/inspectors/signals.md @@ -162,7 +162,7 @@ Angular doesn't send a value for `linkedSignal` nodes. The overlay takes it from ### Exact and sampled values -Exact **set** entries come from a hook on signal writes, which the overlay loads from `@angular/core/primitives/signals`. Before Angular 20.0 the hook doesn't say which signal was written, so the overlay doesn't install it. A webpack build (the `browser` builder) leaves that import to run time, where it fails. In both cases every entry is **sampled**. The overlay matches a write to a node by its name, kind, version and value. It samples everything else each time it reads the page, as **sampled** entries. +The value history is part of the live graph, so it needs Angular 20.1 or later. Exact **set** entries come from a hook on signal writes, which the overlay loads from `@angular/core/primitives/signals`. A webpack build (the `browser` builder) leaves that import to run time, where it fails, so there every entry is **sampled**. The overlay matches a write to a node by its name, kind, version and value. It samples everything else each time it reads the page, as **sampled** entries. In a development build, the Angular compiler names most signals for you. It adds a `debugName` to `signal()`, `computed()`, `linkedSignal()`, `input()`, `model()`, queries, `effect()`, `resource()` and `httpResource()` when the call initializes a class field, a `this.name =` assignment or a variable. The name is the field or variable name.