ng serve with @angular/build: DevTools file search not working

Aperta
#33,510 2 commenti 2 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
angular

Direzione di ricerca

Riproduci il problema con una nuova app Angular usando ng serve e @angular/build, quindi confrontala con Angular 19 usando @angular-devkit/build-angular. Verifica come l'output di serve viene esposto in Chrome o Edge DevTools Sources. Il lavoro è completato quando la ricerca tra file restituisce contenuti in Angular 20+ come in Angular 19 e la regressione pertinente è coperta dai test del progetto.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: @angular/build gemini-triaged
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

angular19 with @angular-devkit/build-angular

Description

When I try to migrate an Angular 20 project from @angular-devkit/build-angular to the new @angular/build, I notice that when running ng serve and opening the browser DevTools → Sources, searching for content across all files does not return any results.

Minimal Reproduction

Angular versions: 20, 21, and 22 (out of the box)
Browser: Edge and Chrome
Operating System: Windows and Linux
SSR: off
Zoneless: off

Steps:

  1. Create a new Angular app with ng new v20.
  2. Run ng serve.
  3. Open the browser and go to DevTools → Sources.
  4. Try to search for content across all files.
Image

Steps:

  1. Create a new Angular app with ng new v22.
  2. Run ng serve.
  3. Open the browser and go to DevTools → Sources.
  4. Try to search for content across all files.
Image
Exception or Error

Your Environment
Angular CLI: 20.3.31
Node: 22.14.0
Package Manager: npm 10.9.2
OS: linux x64
    

Angular: 20.3.25
... common, compiler, compiler-cli, core, forms
... platform-browser, router

Package                      Version
------------------------------------
@angular-devkit/architect    0.2003.31
@angular-devkit/core         20.3.31
@angular-devkit/schematics   20.3.31
@angular/build               20.3.31
@angular/cli                 20.3.31
@schematics/angular          20.3.31
rxjs                         7.8.2
typescript                   5.9.3
zone.js                      0.15.1

---------------------------------------

Angular CLI       : 22.0.5
Angular           : 22.0.5
Node.js           : 24.18.0
Package Manager   : npm 11.16.0
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 22.0.5            │ ^22.0.5           │
│ @angular/cli              │ 22.0.5            │ ^22.0.5           │
│ @angular/common           │ 22.0.5            │ ^22.0.0           │
│ @angular/compiler         │ 22.0.5            │ ^22.0.0           │
│ @angular/compiler-cli     │ 22.0.5            │ ^22.0.0           │
│ @angular/core             │ 22.0.5            │ ^22.0.0           │
│ @angular/forms            │ 22.0.5            │ ^22.0.0           │
│ @angular/platform-browser │ 22.0.5            │ ^22.0.0           │
│ @angular/router           │ 22.0.5            │ ^22.0.0           │
│ rxjs                      │ 7.8.2             │ ~7.8.0            │
│ typescript                │ 6.0.3             │ ~6.0.2            │
│ vitest                    │ 4.1.9             │ ^4.0.8            │
└───────────────────────────┴───────────────────┴───────────────────┘
Anything else relevant?

Angula version: 19 (out of the box)
Browser: Edge and Chrome
Operating System: Windows and Linux
SSR: off

Steps:

  1. Create a new Angular app with ng new v19.
  2. Run ng serve.
  3. Open the browser and go to DevTools → Sources.
  4. Try to search for content across all files.

Result:
The search works correctly in Angular 19.

Image

Angular CLI: 19.2.27
Node: 22.14.0
Package Manager: npm 10.9.2
OS: linux x64

Angular: 19.2.25
... common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package Version

@angular-devkit/architect 0.1902.27
@angular-devkit/build-angular 19.2.27
@angular-devkit/core 19.2.27
@angular-devkit/schematics 19.2.27
@angular/cli 19.2.27
@schematics/angular 19.2.27
rxjs 7.8.2
typescript 5.7.3
zone.js 0.15.1

Lingua principale
TypeScript
Stelle
27k
Fork
11.8k
Merge medio
16h 21m
PR unite (30g)
170

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di angular/angular-cli

Tutte le issue di angular/angular-cli

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.