Template diagnostics not updated in watch mode on Windows when the type-check block is unchanged
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
- #34733 von @Matt-code-d — ohne Merge geschlossen
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Anfängerfreundlichkeit
- 35/100
- Issue-Typ
- Bug
- Klarheit
- Klar beschrieben
- Aktivitätsstatus
- Veraltet
- Tech-Stack
- angular, typescript
- Bereich
- build-system, devtools
Rechercherichtung
Start with the resource invalidation check in packages/angular/build/src/tools/angular/compilation/aot-compilation.ts and the modified file handling in packages/angular/build/src/tools/esbuild/angular/source-file-cache.ts. Trace how resource dependency paths are compared during ng serve watch rebuilds on Windows, then check the existing compilation tests for coverage of that path comparison. Done means template diagnostics refresh on Windows when a template changes without changing its type-check shim, while Linux behavior remains correct.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Command
serve
Is this a regression?
- Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
On Windows, during ng serve, a template edit that changes Angular diagnostics without changing the generated type-check code is not diagnosed: a stray </span> (NG5002) still ends with "Application bundle generation complete", and [attr.width.px] never shows NG8106. Linux and ng build report both correctly.
The resource check that invalidates diagnosticCache (aot-compilation.ts#L334) looks up forward-slash paths from getResourceDependencies() in modifiedFiles, which holds path.normalized backslash paths (source-file-cache.ts#L42), so it never matches on Windows:
modifiedFiles: ["C:\\repro\\src\\app\\app.html"]
resourceDependencies: ["C:/repro/src/app/app.html"]
match: false (Linux: true)
Edits that change the .ngtypecheck.ts shim are still picked up by the TypeScript builder; the others rely on this check alone. A possible fix is hostOptions.modifiedFiles.has(path.normalize(resourceDependency)).
Minimal Reproduction
Repro: https://github.com/te-gis-dev/ng-stale-template-diagnostics (node repro.mjs runs all steps against ng serve and restores the files).
With @angular/build 22.2.7, run ng serve, then:
- Append
</span>tosrc/app/app.html. ExpectedNG5002; actual on Windows: build completes, no error. - Revert, then append
<p [attr.width.px]="1"></p>. ExpectedNG8106warning; actual on Windows: none. - Add a blank line to
src/app/app.ts. The missing diagnostics appear.
| Setup | Stray </span> |
[attr.width.px] |
|---|---|---|
| 22.2.7, Windows 11, Node 26.12.1 | not reported | not reported |
22.2.7, Linux (Docker node:24) |
correct | correct |
Exception or Error
Windows:
Application bundle generation complete.
Linux:
✘ [ERROR] NG5002: Unexpected closing tag "span". It may happen when the tag has already been closed by another tag. For more info see https://www.w3.org/TR/html5/syntax.html#closing-elements-that-have-implied-end-tags [plugin angular-compiler]
Application bundle generation failed.
Your Environment
Angular CLI : 22.2.7
Angular : 22.2.6
Node.js : 26.12.1
Package Manager : npm 11.16.0
Operating System : win32 x64
┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build │ 22.2.7 │ 22.2.7 │
│ @angular/cli │ 22.2.7 │ 22.2.7 │
│ @angular/common │ 22.2.6 │ 22.2.6 │
│ @angular/compiler │ 22.2.6 │ 22.2.6 │
│ @angular/compiler-cli │ 22.2.6 │ 22.2.6 │
│ @angular/core │ 22.2.6 │ 22.2.6 │
│ @angular/forms │ 22.2.6 │ 22.2.6 │
│ @angular/platform-browser │ 22.2.6 │ 22.2.6 │
│ @angular/router │ 22.2.6 │ 22.2.6 │
│ rxjs │ 7.8.2 │ ~7.8.0 │
│ typescript │ 6.0.3 │ 6.0.3 │
└───────────────────────────┴───────────────────┴───────────────────┘
Anything else relevant?
- Windows only; drive-letter casing is not involved.
- Latent on
main/ 22.3.0-rc.0: #34173 marks the component affected through Angular's incremental compilation first, but the lookup is stillfalseon Windows. The check has never matched there since #25940. - On 22.2.x it also locks in the stale cached error fixed by #34173: while it is served, every template edit on Windows is ignored (
repro.mjssteps 1-6).
- Vorherrschende Sprache
- TypeScript
- Sterne
- 27k
- Forks
- 11.8k
- Ø Merge
- 1 T. 2 Std.
- Gemergte PRs (30 T.)
- 225
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus angular/angular-cli
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Offenarea: @angular/build
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
angular/angular-cli#34764 ·
Maintainer antworten meist innerhalb von 1 Tag
-
ng add @angular/ssr fails with TypeError when an NgModule in the app module file has no bootstrap arrayEvtl. vergeben @0z5a hat das heute übernommen. Offenarea: @schematics/angular
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 90/100
angular/angular-cli#34761 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 72/100
angular/angular-cli#34760 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Angular SSR can crash `AngularAppEngine` servers with a single aborted request (22.2.6 regression)Evtl. vergeben @SkyZeroZx hat das vor 1 Tag übernommen. Offenarea: @angular/ssr
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 20/100
angular/angular-cli#34754 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area: @schematics/angular
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 74/100
angular/angular-cli#34730 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in angular/angular-cli
Ähnliche Issues
-
status/need-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
google-gemini/gemini-cli#30384 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
P2
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug ready-for-human
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement good first issue priority: low size: XS
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
vercel-labs/scriptc#3979 ·
Maintainer antworten meist innerhalb von 1 Tag