Template diagnostics not updated in watch mode on Windows when the type-check block is unchanged
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
- #34733 de @Matt-code-d — fechado sem integrar
Avaliação
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Bug
- Clareza
- Claramente especificada
- Status de atividade
- Estagnada
- Stack de tecnologia
- angular, typescript
- Domínio
- build-system, devtools
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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).
- Linguagem predominante
- TypeScript
- Estrelas
- 27k
- Forks
- 11.8k
- Merge médio
- 1d 2h
- PRs com merge (30d)
- 225
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de angular/angular-cli
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Abertaarea: @angular/build
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
angular/angular-cli#34764 ·
Mantenedores costumam responder em até 1 dia
-
ng add @angular/ssr fails with TypeError when an NgModule in the app module file has no bootstrap arrayTalvez já em andamento @0z5a assumiu hoje. Abertaarea: @schematics/angular
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 90/100
angular/angular-cli#34761 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 72/100
angular/angular-cli#34760 ·
Mantenedores costumam responder em até 1 dia
-
Angular SSR can crash `AngularAppEngine` servers with a single aborted request (22.2.6 regression)Talvez já em andamento @SkyZeroZx assumiu há 1 dia. Abertaarea: @angular/ssr
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 20/100
angular/angular-cli#34754 ·
Mantenedores costumam responder em até 1 dia
-
area: @schematics/angular
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 74/100
angular/angular-cli#34730 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de angular/angular-cli
Issues semelhantes
-
status/need-triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
google-gemini/gemini-cli#30384 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
P2
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 84/100
Mantenedores costumam responder em até 1 dia
-
bug ready-for-human
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 60/100
LucasSantana-Dev/Lucky#3150 ·
Mantenedores costumam responder em até 1 dia
-
enhancement good first issue priority: low size: XS
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
vercel-labs/scriptc#3979 ·
Mantenedores costumam responder em até 1 dia