Angular wont reload after making any change

[dombrga]

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

Hello.

I am using WSL2 ubuntu to make an angular app.

The app does not reload after I make any change in any file.

But when I delete package-lock and node_modules, and run npm install again in Windows and not in WSL2, and run the app then make a change, it works perfectly fine.

Thank you!

Minimal Reproduction

1. In wsl2, I installed angular cli by npm i -g @angular/cli
2. ng new
3. npm run start/ng serve
4. The app runs, but when I make a change in the title property in the app.component.ts file, the changes do not reflect automatically.

The terminal just always looks like this whenever I make a change in html or ts files. No error in browser console as well.

Exception or Error

None.

Your Environment

_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI: 17.3.2
Node: 20.11.1
Package Manager: npm 10.2.4
OS: linux x64

Angular: 17.3.2
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1703.2
@angular-devkit/build-angular   17.3.2
@angular-devkit/core            17.3.2
@angular-devkit/schematics      17.3.2
@schematics/angular             17.3.2
rxjs                            7.8.1
typescript                      5.4.3
zone.js                         0.14.4

Anything else relevant?

I am using

1. wsl2 ubuntu
2. visual studio code
3. microsoft edge browser

I just want to reiterate that it works perfectly fine on Windows (after deleting node_modules and package-lock file and doing npm i) and not on wsl2.

Thank you!

[alan-agius4]

This issue has surfaced previously, and it appears that Angular CLI might not be the culprit; instead, it seems to be a bug within WSL2. For further details, you can refer to the discussion here: microsoft/WSL#4739

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