Angular 19 migration build issue

[Harish-Reddyshetty]

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

18

Description

I have upgraded my application from Angular 18 to 19. After a successful migration, any code changes I make are not reflected in the browser, and the application does not auto-reload when I modify the code. Even after making changes, the old version is still displayed.

i have tried below few things

1. --no-hmr
2. Removed package-lock.json, .angular .vite and reinstalled them.
3. adde live reload in angular.json

Minimal Reproduction

After the migration i have run the command ng s . when i open the local server the changes are not reflected in the broswer

Exception or Error

Your Environment

Angular CLI: 19.2.3
Node: 20.19.0
Package Manager: npm 10.8.2
OS: linux x64

Angular: 19.2.2
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
... service-worker

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.1902.3
@angular-devkit/build-angular      19.2.3
@angular-devkit/core               19.2.3
@angular-devkit/schematics         19.2.3
@angular/cdk                       19.2.3
@angular/cli                       19.2.3
@angular/google-maps               19.2.3
@angular/material                  19.2.3
@angular/material-moment-adapter   19.2.3
@schematics/angular                19.2.3
rxjs                               7.8.2
typescript                         5.5.4
zone.js                            0.15.0

Anything else relevant?

No response

[alan-agius4]

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?

You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

This might be related to your directory structure so its really important to get an accurate repro to diagnose this.