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

Don't known / other

Is this a regression?

No

Description

When running an Angular SSR application with a Express server, routes configured with renderMode: 'client' are still being executed on the server. However, the same routes are correctly skipped during server execution when using ng serve.

Steps to Reproduce:

• git clone -b render-mode https://github.com/sajay-g/ssr-native-fed-poc-.git
• npm install
• ng build shell
• ng build mfe1
• node dist/shell/server/server.mjs
• node dist/mfe1/server/server.mjs
• Visit http://localhost:4200/mfe1

Please provide a link to a minimal reproduction of the bug

https://github.com/sajay-g/ssr-native-fed-poc-.git

Please provide the exception or error you saw

The component is executed on the server, and the log Loading MFE1 Component appears in the server console.

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

Angular CLI: 19.2.14
Node: 20.18.2
Package Manager: npm 11.0.0
OS: darwin x64

Angular: 19.2.14
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router, ssr

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1902.14
@angular-devkit/build-angular   19.2.14
@angular-devkit/core            19.2.14
@angular-devkit/schematics      19.2.14
@schematics/angular             19.2.14
rxjs                            7.8.2
typescript                      5.6.3
zone.js                         0.15.1

Anything else?

Additional Notes
This application uses @angular/architect native module federation and CommonEngine.

If I try to switch to AngularNodeAppEngine, it works as expected with ng serve, but fails when run via Node Express server, throwing: Angular app engine manifest is not set