Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Angular 12] Node 16.0.0: Creating new angular workspace failed

See original GitHub issue

🐞 Bug report

Command (mark with an `x`)

new
build
serve
test
e2e
generate
add
update
lint
extract-i18n
run
config
help
version
doc

Is this a regression?

N/A

Description

Angular CLI is unable to create an angular workspace if the runtime is Node 16.0.0

🔬 Minimal Reproduction

❯ npx @angular/cli@12.0.0-rc.0 new web-apps --create-application false

🔥 Exception or Error


⠦ Installing packages (yarn)...warning @angular/cli > pacote > @npmcli/run-script > node-gyp > request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
warning @angular/cli > pacote > @npmcli/run-script > node-gyp > request > har-validator@5.1.5: this library is no longer supported
error @angular/animations@12.0.0-rc.0: The engine "node" is incompatible with this module. Expected version ">=12.14.1 <16.0.0". Got "16.0.0"
error Found incompatible module.
✖ Package install failed, see above.
The Schematic workflow failed. See above.

🌍 Your Environment


❯ node --version
v16.0.0
❯ yarn --version
1.22.10
❯ sw_vers
ProductName:	macOS
ProductVersion:	11.2.3
BuildVersion:	20D91

Anything else relevant?

Issue Analytics

State:
Created 2 years ago
Comments:10 (6 by maintainers)

Top GitHub Comments

2reactions

josephperrottcommented, Apr 26, 2021

I have opened https://github.com/angular/angular/pull/41820 to make our supported versions clearer as the understanding of the terms Node.js uses around their versions has solidified.

As noted on Node.js’s Releases page, only active LTS and maintenance LTS versions should be used for production applications, and as such they are the only ones that Angular supports.

Specific to version 16 usage, it will become an LTS version, however it is not slated to become LTS until 2021-10-26. As @alan-agius4 noted, you should be able to use it while using the --ignore-engines flag, though it will not be officially supported by Angular until after it becomes an LTS version.

0reactions

angular-automatic-lock-bot[bot]commented, May 31, 2021

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