Angular 17.3 ngOnInit running infinite loop with defer block about angular HOT 12 CLOSED

Quick update: the fix for this issue was merged and released as a part of Angular v17.3.2 (available on NPM). Please let us know if you still see the issue after updating to v17.3.2.

from angular.

Or do I have to wait for the next published release?

There will be a release later today that includes the fix.

from angular.

Its fixed! Works great! (like it did with 17.0.1). Thank you very much for listening to my request, and investigating / attacking the problem! I'm very grateful!

from angular.

Please provide a runnable reproduction, either in a Github repository or Stackblitz.

from angular.

Done! Not sure if you can see the code and replicate the issue..
UPDATE STACKBLITZ

Here is what I managed to put onto Stackblitz
https://stackblitz.com/edit/stackblitz-starters-aeguwd?file=src%2Fproject-parent%2Fproject-parent.routes.ts

from angular.

@dreamstar-enterprises Thank you for the reproduction. @AndrewKushnir I simplified the reproduction quite a bit here: https://stackblitz.com/edit/stackblitz-starters-bmouvm. This seems pretty similar to #54864 where a component with imports causes an issue.

from angular.

Thanks. I don't know what's causing it, but it just refuses to load both components in the defer block. project navigation gets repeatedly loaded, and router outlet, won't load project-detail (which is an empty component anyway). But I can load each component, when I comment one or the other out. The links also lose all their relative link referencing....

from angular.

from angular.

For more information, this does work! (But, i have other components, where I do need multiple components in a defer block, so, not sure what's going on with Angular 17.3). If put the components in nested defer blocks, inside the main defer block it also, strangely, works, but the components lose their relative link referencing, and reference from the app root...

from angular.

@dreamstar-enterprises I've confirmed that the root cause of this issue is the same as the one in #54864. We are working on a fix and I'll share an update once the fix is available.

from angular.

Thank you! I really, really appreciate it. (I'll try to roll back to 17.01 if I can in the meantime)

from angular.

Thank you. The issue seems closed now. Do you know how I, myself, could get the changes. Or do I have to wait for the next published release?

from angular.