-
Notifications
You must be signed in to change notification settings - Fork 26.8k
Closed as not planned
Description
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
Angular V20.x isn't released yet, but I'm seeing debug_node*.mjs code showing up in production builds for zoneless apps. I've attached the corresponding stats.json.
To reproduce:
1. ng new repro‐app --defaults
2. choose zoneless
3. cd repro-app
4. ng build --configuration production --source-map=false
5. Inspect dist/repro-app/stats.json or .mjs bundles
Observed
node_modules/@angular/core/fesm2022/debug_node-sP8Ihhla.mjs is still in the generated chunks, imported by signal-.mjs and root_effect_scheduler-*.mjs.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 20.0.0-next.9
Node: 22.15.0
Package Manager: npm 10.9.2
OS: darwin arm64
Angular: 20.0.0-next.9
... build, cli, common, compiler, compiler-cli, core, forms
... platform-browser, router
Package Version
------------------------------------------------------
@angular-devkit/architect 0.2000.0-next.9
@angular-devkit/core 20.0.0-next.9
@angular-devkit/schematics 20.0.0-next.9
@schematics/angular 20.0.0-next.9
rxjs 7.8.2
typescript 5.8.3
zone.js 0.15.0
Anything else?
No response
Metadata
Metadata
Assignees
Labels
No labels