ssr does not render routes with custom matcher

[dklmuc]

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

Don't known / other

Is this a regression?

Yes

Description

The new SSR implementation does not seem to work with custom route matcher.

The simple reproduction in linked repo is set to render all routes server side and contains two routes (one by path, one by custom matcher). When serving the app it shows the problem.

Please provide a link to a minimal reproduction of the bug

https://github.com/dklmuc/angular-ssr

Please provide the exception or error you saw

The defined route by path (/path) is rendered as expected but the one defined with a custom matcher (/matcher) is not rendered at all and results in a 404 Cannot GET /matcher.

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

Angular CLI: 19.0.6
Node: 18.20.5
Package Manager: npm 10.8.2
OS: linux x64

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

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1900.6
@angular-devkit/build-angular   19.0.6
@angular-devkit/core            19.0.6
@angular-devkit/schematics      19.0.6
@angular/cli                    19.0.6
@angular/ssr                    19.0.6
@schematics/angular             19.0.6
rxjs                            7.8.1
typescript                      5.6.3
zone.js                         0.15.0

Anything else?

Same problem after building the app and starting the bundle.

[alan-agius4]

Supporting this could be challenging because routes need to be statically available, and the route tree must be serializable – something that isn't possible with a function.

We previously discussed adding more constraints when using SSR, and this might need to be one of them. For now, I'll give it some more thought to see if there's a workable solution.

[angular-robot]

This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list.

You can find more details about the feature request process in our documentation.