v19.1 with SSR not building/responding in dev mode: The operation was aborted due to timeout

[zip-fa]

Command

build

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

19.0

Description

Hey. Updating v19.0.x app to v19.1.x breaks build with this error:

✘ [ERROR] An error occurred while extracting routes.

Routes extraction was aborted.
TimeoutError: The operation was aborted due to timeout

No routes, no code, no logic.
Minimal repro available here: https://github.com/zip-fa/19-1-endless-build

Switching from server config:

"server": "src/main.server.ts",
        "outputMode": "server",
        "ssr": {
          "entry": "src/server.ts"
        }

To static config:

"outputMode": "static"

immediately helps

Minimal Reproduction

nx build 19-1-endless-build

Exception or Error

Your Environment

ng version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI: 19.1.2
Node: 22.13.0
Package Manager: npm 10.9.2
OS: darwin arm64

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

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1901.2
@angular-devkit/build-angular   19.1.2
@angular-devkit/core            19.1.2
@angular-devkit/schematics      19.1.2
@angular/cli                    19.1.2
@angular/ssr                    19.1.2
@schematics/angular             19.1.2
rxjs                            7.8.1
typescript                      5.7.3
zone.js                         0.15.0

Anything else relevant?

No response

[Releef]

I have the same issue. Setting my node version to 20.11.1 seems to work for me. It could be worth trying out for yourself as a temporary fix.

[xidedix]

The same here. Setting outputMode: "static" doesn’t help either.

[SaeedDev94]

An error occurred while extracting routes.

Routes extraction was aborted.
TimeoutError: The operation was aborted due to timeout

"@angular/cli": "^19.1.2"
"@angular/ssr": "^19.1.2"
"@angular/core": "^19.1.1"

nodejs: v22.13.0

[SaeedDev94]

It's not just build command, ng serve also doesn't work for me, I'm getting timeout error !!
I can't do anything with new version, wt... !!

[SaeedDev94]

I have the same issue. Setting my node version to 20.11.1 seems to work for me. It could be worth trying out for yourself as a temporary fix.

I prefer to downgrade the ng version instead of node !! -_-

[alan-agius4]

This issue doesn't appear to be related to the Node.js version. Upon investigation, I observed that the problem arises specifically when using withEnabledBlockingInitialNavigation. In general, it is not recommended to use this feature together with hydration.

[SaeedDev94]

This issue doesn't appear to be related to the Node.js version. Upon investigation, I observed that the problem arises specifically when using withEnabledBlockingInitialNavigation. In general, it is not recommended to use this feature together with hydration.

I removed withEnabledBlockingInitialNavigation and the problem solved but this breaking change shouldn't have a migration ?
withEnabledBlockingInitialNavigation and provideClientHydration was working in v19.0.x together ...

[alan-agius4]

I have a fix in progress that should address this issue and unblock it. As a side note, withEnabledBlockingInitialNavigation should generally not be used alongside provideClientHydration. We should consider issuing a warning about this, as this method is intended specifically for use in scenarios involving SSR with destructive hydration.

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