[es-build] Browser directory created in outputPath

[ssougnez]

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

I have an Angular application configure as below:

"outputPath": "../MyNetApplication/wwwroot",

When using webpack build, the compiled files of the Angular application went directly in wwwroot so I could publish my .NET application and it worked directly.

I tried to switch to es-build, however, after the build, the compiled files of the Angular application end up into "../MyNetApplication/wwwroot/browser" which prevents me from publishing the .NET application as this would not work.

It seems weird to me that the outputPath settings of angular.json is only partially honored.
According to me, this settings should be used and not altered during the compilation.

Minimal Reproduction

Just create a new Angular application using angular/cli 17 and run ng build.
The files will be located under dist/ng17/browser.

Exception or Error

No response

Your Environment

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1700.0
@angular-devkit/build-angular   17.0.0
@angular-devkit/core            17.0.0
@angular-devkit/schematics      17.0.0
@angular/cli                    17.0.0
@schematics/angular             17.0.0
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.2

Anything else relevant?

No response

[JoostK]

Closing as duplicate of #26304, seems to have been submitted twice by accident.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}