Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

library builder: entry points a/b and a-b are built into the same bundle

未關閉
#34,128 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

@alan-agius4 已經在處理了。

開始於 2026年9月19日。

評估

這個 Issue 還沒有評估資料。

描述

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

Two entry points whose names differ only by / vs - (like zz/child and zz-child) get the same bundle name. The build passes with exit 0, one entry point's code overwrites the other's, and both exports point at the same file.

Minimal Reproduction
  1. projects/lib/zz/child/public-api.ts: export const NESTED = 'nested';
  2. projects/lib/zz-child/public-api.ts: export const FLAT = 'flat';
  3. entryPoints: "./zz-child": "projects/lib/zz-child/public-api.ts" and "./zz/child": "projects/lib/zz/child/public-api.ts"
  4. ng build mylib exits 0, fesm2022 has a single mylib-zz-child.mjs with only NESTED, and both ./zz-child and ./zz/child in exports point at it
  5. import { FLAT } from 'mylib/zz-child' fails in the consumer
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
pnpm 11
macOS 25.6, 14 cores, 24 GB
Anything else relevant?

No response

主要語言
TypeScript
星號
27k
分支
11.8k
平均合併
17 小時 21 分鐘
30 天內合併 PR
181

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

angular/angular-cli 的其他 Issue

查看 angular/angular-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。