-
Notifications
You must be signed in to change notification settings - Fork 12k
Closed
Labels
angular/build:applicationarea: @angular-devkit/build-angularfreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelytype: bug/fix
Description
Command
serve
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
After changing the "build.builder" to "@angular-devkit/build-angular:browser-esbuild", as described here, the app builds but does not bootstrap, throwing the following error:
ApplicationInitStatus is undefined
The default webpack builder works fine.
Minimal Reproduction
- Clone the https://github.com/Klaster1/timer-5
- Switch to the "esbuild" branch.
- Run "npm i", "ng serve", navigate to http://127.0.0.1:4200.
Exception or Error
No response
Your Environment
Angular CLI: 16.0.0
Node: 18.15.0
Package Manager: npm 9.5.0
OS: win32 x64
Angular: 16.0.0
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, language-service, material, platform-browser
... platform-browser-dynamic, router, service-worker
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1600.0
@angular-devkit/build-angular 16.0.0
@angular-devkit/core 16.0.0
@angular-devkit/schematics 16.0.0
@schematics/angular 16.0.0
rxjs 7.8.1
typescript 5.0.4
Anything else relevant?
No response
Metadata
Metadata
Assignees
Labels
angular/build:applicationarea: @angular-devkit/build-angularfreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelytype: bug/fix