fix(@angular/build): perform incremental background file updates with component updates

[clydin]

When HMR is enabled, a change to a lazy route component template may alter the names of lazy chunks. These lazy chunks must be updated within the development server so that any later non-HMR based update will have access to these chunks. To support this, the incremental results from the build process can now emit background file updates that will provide output file changes without triggering client updates.

[alan-agius4]

LGTM, I am no longer able to replicate the problem with this change.

NIT: as a followup we should add a test that verifies when accessing main.js vite does not error.

[dgp1130]

The changes were merged into the following branches: main, 19.1.x

[p1n5u]

@alan-agius4 Do you know when the next 19.1.x release will be available with this fix? I’m currently trying to upgrade my application from 19.0.x to 19.1.x, but this bug prevents ng serve from working as soon as I use dynamic imports in my code (not only when lazy-loading routes).

[alan-agius4]

@p1n5u, this update was released last week. I believe you may be encountering a different issue.

[p1n5u]

@alan-agius4 you are right. sorry for the noise. will try to create a minimal reproduction example and open an issue.

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