@ngtools/webpack keeps a `const enum` import when it rewrites the import declaration ("export ... was not found")
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 72/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- angular, typescript, webpack
- Ambito
- backend, build-system
Direzione di ricerca
Start by reading elide_imports.ts and the related fix in #34594; the issue identifies the import rewrite as the likely failure point. Reproduce with the linked project using npm ci && npm run build, then trace how the combined Period and PeriodFormatter import is rewritten. Done when the build succeeds for that reproduction and the const enum import is elided without breaking the runtime value.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Which @angular/* package(s) are the source of the bug?
@ngtools/webpack (via @angular-devkit/build-angular, browser builder)
Is this a regression?
Yes. The last version that works is @angular-devkit/build-angular 22.1.9. It fails from 22.2.0 through 22.3.0 (the latest at the time of writing), whatever the @angular/* framework version: build-angular 22.1.9 with Angular 22.2.0 works, and build-angular 22.2.0 with Angular 22.1.8 fails.
Description
When one import statement brings in a const enum together with a runtime value that is used only in type positions (for example a class that is only a constructor parameter type), the webpack build fails:
./src/app/app.component.ts:1:0-34 - Error: export 'Period' (imported as 'Period') was not found in './period' (possible exports: PeriodFormatter)
// period.ts
import { Injectable } from '@angular/core';
export const enum Period {
Month = 'month',
Quarter = 'quarter',
}
@Injectable({ providedIn: 'root' })
export class PeriodFormatter {
format(period: string): string {
return `Period: ${period}`;
}
}
// app.component.ts
import { Component } from '@angular/core';
import { Period, PeriodFormatter } from './period';
@Component({ selector: 'app-root', template: '<p>{{ label }}</p>' })
export class AppComponent {
protected readonly label: string;
constructor(formatter: PeriodFormatter) {
this.label = formatter.format(Period.Month);
}
}
What seems to happen, judging from elide_imports.ts: PeriodFormatter is only referenced from a type node, so its specifier is classed as an unused runtime value and the declaration is rewritten without it. The comment there notes that TypeScript skips its own import elision for a declaration a transformer replaced. Period counts as used (Period.Month is an identifier reference), so it is kept, but TypeScript has inlined the const enum and would normally drop the specifier. The rewritten declaration still imports Period, which has no runtime export.
Notes:
- The constructor parameter is not essential: any runtime value used only in type positions in the same statement triggers it, for example a field typed
PeriodFormatter | undefined. - Not needed: a barrel, tsconfig
paths, or any non-default compiler option.ngcalone emits the file correctly. - Possibly related: #34594 (22.2.6), which fixed type-only specifiers but not this case.
- Workarounds: a regular
enum, or importing the const enum in its own import statement.
| @angular/* | @angular-devkit/build-angular | result |
|---|---|---|
| 22.1.8 | 22.1.9 | builds |
| 22.2.0 | 22.1.9 | builds |
| 22.1.8 | 22.2.0 | fails |
| 22.2.0 | 22.2.0 | fails |
| 22.2.4 – 22.2.6 | 22.2.4 – 22.2.7 | fails |
| 22.2.7 | 22.2.8 | fails |
| 22.3.0 | 22.3.0 | fails |
Please provide a link to a minimal reproduction of the bug
https://github.com/IT-CASADO/const-enum-elision-repro
npm ci && npm run build
Please provide the exception or error you saw
./src/app/app.component.ts:1:0-34 - Error: export 'Period' (imported as 'Period') was not found in './period' (possible exports: PeriodFormatter)
Please provide the environment you discovered this bug in
Angular CLI : 22.2.7
Angular : 22.2.6
@angular-devkit/build-angular : 22.2.7
TypeScript : 6.0.3
Node : 24.22.3
OS : Windows 11
- Lingua principale
- TypeScript
- Stelle
- 27k
- Fork
- 11.8k
- Merge medio
- 1g 2h
- PR unite (30g)
- 225
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di angular/angular-cli
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Apertaarea: @angular/build
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
angular/angular-cli#34764 ·
I maintainer di solito rispondono entro 1 giorno
-
ng add @angular/ssr fails with TypeError when an NgModule in the app module file has no bootstrap arrayForse già presa @0z5a l’ha presa oggi. Apertaarea: @schematics/angular
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
angular/angular-cli#34761 ·
I maintainer di solito rispondono entro 1 giorno
-
Angular SSR can crash `AngularAppEngine` servers with a single aborted request (22.2.6 regression)Forse già presa @SkyZeroZx l’ha presa 1 giorno fa. Apertaarea: @angular/ssr
Difficoltà 4/5 3-5 giorni Idoneità per principianti 20/100
angular/angular-cli#34754 ·
I maintainer di solito rispondono entro 1 giorno
-
area: @schematics/angular
Difficoltà 3/5 1-2 giorni Idoneità per principianti 74/100
angular/angular-cli#34730 ·
I maintainer di solito rispondono entro 1 giorno
-
area: @angular/build
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
angular/angular-cli#34728 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di angular/angular-cli
Issue simili
-
status/need-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
google-gemini/gemini-cli#30384 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
P2
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno
-
bug ready-for-human
Difficoltà 2/5 1-3 ore Idoneità per principianti 60/100
LucasSantana-Dev/Lucky#3150 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement good first issue priority: low size: XS
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
vercel-labs/scriptc#3979 ·
I maintainer di solito rispondono entro 1 giorno