ng build lib --watch output css not changes sometimes

[kolkov]

Hi! If I change scss file in library, app refreshes, but style not changes sometimes.

Angular CLI: 9.0.0-rc.3
Node: 12.13.1
OS: win32 x64
Angular: 9.0.0-rc.3
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.900.0-rc.3
@angular-devkit/build-angular      0.900.0-rc.3
@angular-devkit/build-ng-packagr   0.900.0-rc.3
@angular-devkit/build-optimizer    0.900.0-rc.3
@angular-devkit/build-webpack      0.900.0-rc.3
@angular-devkit/core               9.0.0-rc.3
@angular-devkit/schematics         9.0.0-rc.3
@ngtools/webpack                   9.0.0-rc.3
@schematics/angular                9.0.0-rc.3
@schematics/update                 0.900.0-rc.3
ng-packagr                         9.0.0-rc.1
rxjs                               6.5.3
typescript                         3.6.4
webpack                            4.41.2

[kolkov]

But if I remove or add some character, this workes with refresh.

[alan-agius4]

Hi @kolkov, can you please clarify if correct css is not reflected in the consuming application or at a library level in the dist folder?

[kolkov]

@alan-agius4 If I understand correctly lib compiles properly. And I can't debug my lib. I can't see debug info in chrome dev tools.

I remove !important; from host, but I still see:

and in lib folder I see:

[alan-agius4]

Mostly likely this is a duplicate of #13588

Will take a look in the coming days

[alan-agius4]

I had a look at it, and it seems not related to the issue above, also as mentioned above by the reported it doesn't happen consistently.

The problem seems to be related and webpack notifications to the browser. This is being the changes are in the served bundle it's just not reflected in the browser, as when a user does hit CTRL + F5 the style change is visible.

[kolkov]

This fixed in rc.4. thanks!

[alan-agius4]

In that case I am going to close the issue.

If the problem persists, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.

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