[browser-esbuild] in live reload mode @imported saas styles not reflected in frontend without manully restarting server

[d9j]

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

maybe related to this
#23815

first start project with live reload enabled e.g
ng serve

inside any angular components scss file use @import another scss file . for example .
@import './mycomponent/another.scss';

then edit another.scss file to apply styles you expect to reflect in front end. upon saving changes of another.scss file. you will see no changes in front end reflected unless you restart dev browser-esbuild server.

Minimal Reproduction

maybe related to this
#23815

first start project with live reload enabled e.g

ng serve

inside any angular components scss file use @import another scss file . for example .
@import './mycomponent/another.scss';

then edit another.scss file to apply styles you expect to reflect in front end. upon saving changes of another.scss file. you will see no changes in front end reflected unless you restart dev browser-esbuild server.

Exception or Error

No response

Your Environment

Angular CLI: 16.2.0
Node: 18.16.0
Package Manager: npm 9.5.1
OS: darwin arm64

Angular: 16.2.0
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, material, platform-browser, platform-browser-dynamic
... router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1602.0
@angular-devkit/build-angular   16.2.0
@angular-devkit/core            16.2.0
@angular-devkit/schematics      16.2.0
@schematics/angular             16.2.0
rxjs                            7.8.1
typescript                      4.9.5
zone.js                         0.13.0

Anything else relevant?

No response

[iKrishnaSahu]

Facing the same issue in my monorepo with esbuild in latest 17rc version

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