Angular 19 SSR Build Fails with Node.js@22.2.0, (Resolved by Upgrading to Node.js@22.14.0)

[StefanKern]

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

Don't known / other

Is this a regression?

Yes

Description

After spending several hours troubleshooting why the SSR build was failing, it was discovered that upgrading to the latest Node.js version resolved the issue. This suggests there must be a bug when using Node.js@22.2.0, as Angular SSR applications do not build with this version. A bug report is being opened to address this compatibility issue.

Created app:

...>ng new angularapp
√ Which stylesheet format would you like to use? Sass (SCSS)     [ https://sass-lang.com/documentation/syntax#scss
          ]
√ Do you want to enable Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering)? Yes
√ Would you like to use the Server Routing and App Engine APIs (Developer Preview) for this server application? No

According to https://angular.dev/reference/versions, this version should be compatible, but just isn't. It just hangs, shows building forever and does not provide any meaningful output (even with verbose).

I hope this helps someone who is stuck with a similar issue.

(used angular version: Angular CLI: 19.2.4)

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

There was no error, the build was just in an endless loop and now files where generated, no errors where shown (even with --verbose)

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

Angular CLI: 19.2.4
Node: 22.2.0 <-- was then working with 22.14.0
Package Manager: npm 10.8.1
OS: win32 x64

Angular:
...

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1902.4 (cli-only)
@angular-devkit/core         19.2.4 (cli-only)
@angular-devkit/schematics   19.2.4 (cli-only)
@schematics/angular          19.2.4 (cli-only)

Anything else?

No response

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