Which @angular/* package(s) are the source of the bug?

Don't known / other

Is this a regression?

Yes

Description

Hello,

When i try to migrate to version >20.2.0, i started receiving an error where i can't open the microfrontend i have due to the following error.

Moreover, this error is not reproducable when serving the frontends locally, however it only appears on the deployed version. I doubted that maybe:

• some cors errors are happenning, but it looks fine.
• the js chunks and remote entry are being loaded in the correct order, but maybe they are being executed in a different order. I am not sure.

To give a clearer image of the settings i have, check the following repos i created.
https://github.com/kindy91/shell
https://github.com/kindy91/mf1

The shell loads the routes of the microfrontend and injects them. The error happens when routing to the mf routes from the shell and happens only on the deployed version, not locally.

Finally, i give you the exact library updates that bring this about.

I am not sure where is the problem here to be honest.

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

Please provide the environment you discovered this bug in (run ng version)

Angular CLI: 20.2.0
Node: 22.12.0
Package Manager: npm 10.9.0
OS: linux x64
    

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

Package                         Version
---------------------------------------
@angular-devkit/architect       0.2002.0
@angular-devkit/build-angular   20.2.0
@angular-devkit/core            20.2.0
@angular-devkit/schematics      20.2.0
@angular/cdk                    20.2.0
@angular/cli                    20.2.0
@angular/material               20.2.0
@schematics/angular             20.2.0
rxjs                            7.8.2
typescript                      5.8.3
zone.js                         0.15.1

Anything else?

I am not sure what is causing this, and if it is due to my hosting env or it's a generic bug introduced with >v20.2.0