Esbuild miss css file when specifying inject: false and bundleName in angular.json style section

[leo6104]

Command

serve/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

When we setup angular.json style part like this,

              {
                "input": "projects/styled-components/scss/line-awesome/line-awesome.scss",
                "bundleName": "styles-lineawesome",
                "inject": false
              },

It should create styles-lineawesome.css in esbuild compile.

But, with esbuild, it create styles-lineawesome.[HASHED].css file.

Minimal Reproduction

Exception or Error

It should create `styles-lineawesome.css` in esbuild compile. 

But, with esbuild, it create `styles-lineawesome.[HASHED].css` file.

Your Environment

Angular CLI: 16.0.0-rc.2
Node: 16.19.0
Package Manager: npm 8.19.3
OS: darwin x64

Angular: 16.0.0-rc.3
... animations, common, compiler, compiler-cli, core, elements
... forms, localize, platform-browser, platform-browser-dynamic
... platform-server, router, service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1600.0-rc.1
@angular-devkit/build-angular   16.0.0-rc.1
@angular-devkit/core            16.0.0-rc.1
@angular-devkit/schematics      16.0.0-rc.2
@angular/bazel                  15.2.6
@angular/cdk                    16.0.0-rc.1
@angular/cli                    16.0.0-rc.2
@angular/material               16.0.0-rc.1
@angular/youtube-player         16.0.0-rc.1
@nguniversal/builders           16.0.0-next.0
@nguniversal/common             16.0.0-next.0
@nguniversal/express-engine     16.0.0-next.0
@schematics/angular             16.0.0-rc.2
ng-packagr                      16.0.0-rc.1
rxjs                            7.8.0
typescript                      5.0.3

Anything else relevant?

No response

[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.}