Spread operator slow with `application` builder
- Lingua principale
- TypeScript
- Stelle
- 27k
- Fork
- 11.8k
- Merge medio
- 14h 23m
- PR unite (30g)
- 162
Descrizione
### Which @angular/* package(s) are the source of the bug?
compiler
### Is this a regression?
No
### Description
Hello,
I noticed that the spread operator is significantly slower (sometimes more than 2x slower) when using vite instead of webpack.
This doubles the loading time of some of our components.
In my [minimal reproduction](https://github.com/jopelle1/repro-angular-vite), I get an average of 10ms with webpack and 35ms with vite, with both firefox and chrome.
Is this indeed an issue with angular and is there any way to fix it?
Thank you
### Please provide a link to a minimal reproduction of the bug
https://github.com/jopelle1/repro-angular-vite
### Please provide the environment you discovered this bug in (run `ng version`)
```true
Angular CLI: 17.3.11
Node: 18.20.4
Package Manager: npm 10.8.2
OS: linux x64
Angular: 17.3.12
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1703.11
@angular-devkit/build-angular 17.3.11
@angular-devkit/core 17.3.11
@angular-devkit/schematics 17.3.11
@angular/cli 17.3.11
@schematics/angular 17.3.11
rxjs 7.8.1
typescript 5.4.5
zone.js 0.14.10
```
### Anything else?
_No response_
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia con la riproduzione minima collegata, jopelle1/repro-angular-vite, e confronta i tempi dell’operatore spread con l’application builder usando Vite e webpack. Traccia i percorsi coinvolti di Angular compiler e application builder, quindi verifica se il divario di prestazioni segnalato è stato risolto o caratterizzato chiaramente.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- angular, typescript, vite
- Ambito
- build-system, performance
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100