library builder: a name re-exported through two "export *" paths is dropped from the bundle

Aperta
#34,130 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@alan-agius4 ci sta già lavorando.

Dal 20/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

angular/build:library area: @angular/build gemini-triaged
Command

build

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

Found while testing #34106 cc @alan-agius4

When the same name is reached through two export * paths, and each of those files re-exports it by name from a module bundle treats as external (a sibling entry point, or a package like @angular/core), the name is dropped from the FESM bundle and from the .d.ts. The re-export becomes a bare side-effect import. Exit 0, no warning.

Hit on ng-zorro-antd: ng-zorro-antd/i18n loses NZ_DATE_LOCALE, so import { NZ_DATE_LOCALE } from 'ng-zorro-antd/i18n' stops compiling. ng-packagr keeps it.

Minimal Reproduction
  1. projects/lib/src/a.ts: export { InjectionToken } from '@angular/core';
  2. projects/lib/src/b.ts: the same line
  3. projects/lib/src/public-api.ts: export * from './a'; and export * from './b';
  4. one entry point, ".": "projects/lib/src/public-api.ts"
  5. build: fesm2022/lib.mjs and types/lib.d.ts are each a single line, import "@angular/core";

ng-packagr on the same sources emits export { InjectionToken } from '@angular/core'; in both. A consumer gets TS2305 at build time and "does not provide an export named" at runtime.

Exception or Error
Your Environment
@angular/build built from #34106 (005e05ee) with the repo's own bazel build
Angular CLI 22.1.8
Angular 22.1.7
Node 24.16.0
npm 11.13.0
macOS 26.6, 14 cores, 24 GB
Anything else relevant?

It's rolldown, not builder. rolldown 1.2.8 alone, no Angular: an entry that stars a.js and b.js, each doing export { EXT } from 'ext' with ext external, outputs import "ext" with an empty exports list, and reports no warning even with an onwarn handler. Node keeps the name in that shape (the namespace has EXT) and only drops it when the two paths resolve to different bindings, which is the case the spec's ambiguity rule is for.

One export * path survives, and so does one named re-export plus one star. Other names in the same files are unaffected, only the duplicated one is lost.

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

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.