@ngtools/webpack keeps a `const enum` import when it rewrites the import declaration ("export ... was not found")
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 72/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- angular, typescript, webpack
- Área
- backend, build-system
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Lenguaje dominante
- TypeScript
- Estrellas
- 27k
- Forks
- 11.8k
- Merge medio
- 1 d 2 h
- PR fusionados (30 d)
- 225
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de angular/angular-cli
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Abiertoarea: @angular/build
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
angular/angular-cli#34764 ·
Los mantenedores suelen responder en 1 día
-
ng add @angular/ssr fails with TypeError when an NgModule in the app module file has no bootstrap arrayPosiblemente ocupada @0z5a la tomó hoy. Abiertoarea: @schematics/angular
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
angular/angular-cli#34761 ·
Los mantenedores suelen responder en 1 día
-
Angular SSR can crash `AngularAppEngine` servers with a single aborted request (22.2.6 regression)Posiblemente ocupada @SkyZeroZx la tomó hace 1 día. Abiertoarea: @angular/ssr
Dificultad 4/5 3-5 días Aptitud para principiantes 20/100
angular/angular-cli#34754 ·
Los mantenedores suelen responder en 1 día
-
area: @schematics/angular
Dificultad 3/5 1-2 días Aptitud para principiantes 74/100
angular/angular-cli#34730 ·
Los mantenedores suelen responder en 1 día
-
area: @angular/build
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
angular/angular-cli#34728 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de angular/angular-cli
Issues similares
-
status/need-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
google-gemini/gemini-cli#30384 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
P2
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
bug ready-for-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 60/100
LucasSantana-Dev/Lucky#3150 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue priority: low size: XS
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
vercel-labs/scriptc#3979 ·
Los mantenedores suelen responder en 1 día