-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node.js v22.2 causes ng build hangs up #27674
Comments
Does this repro using Angular 18 RCs? |
@JoostK Yes, it reproduces the same situation even after
|
Unfortunately, this is a regression introduced by Node.js, and it's not something we can address on our end. For more details, see: Node.js Issue #53097. |
It seems that the "regression" was intentional from Node.js' perspective. Unfortunately, this breaking behaviour happened in a minor version of Node.js, We will need to put in some work to address it on our end as it's not as trivial to solve. |
There has been a revert in Node.js that will fix this in their next release. See: nodejs/TSC#1566 (comment) for more information. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Command
build
Is this a regression?
The previous version in which this bug was not present was
No response
Description
When the Node.js version is v22.2.0 (released on 2024-05-15), the
ng build
command hangs up. Node.js v22.1.0 doesn't.Angular CLI is not supporting that version of Node.js officially, but on Firebase App Hosting, the build environment is using Node.js v22.2 today by default. So it is an easy situation for developers to get stumped.
My workaround is to set
engines.node
field inpackage.json
as"20"
. App Hosting builder can determine the Node.js version to install.Minimal Reproduction
ng new
on@angular/cli@latest
(v17.3.7)ng build
Building...
and never finished.Exception or Error
No response
Your Environment
Anything else relevant?
No response
The text was updated successfully, but these errors were encountered: