Skip to content

docs: cover ng update stopping on a Node.js version message - #3788

Open
armando-navarro wants to merge 1 commit into
angular:mainfrom
armando-navarro:b14-upgrade-guide-node-version
Open

armando-navarro wants to merge 1 commit into
angular:mainfrom
armando-navarro:b14-upgrade-guide-node-version

Conversation

@armando-navarro

Copy link
Copy Markdown
Collaborator

Fixes #3786

Adds a bullet under "Other notes" in docs/version-21-upgrade.md for readers whose ng update stops with The Angular CLI requires a minimum Node.js version of ....

Verification

On 2026-10-02, with Node.js 22.22.1, which Angular 21 supports and Angular CLI 22 does not:

  • ng update @angular/fire and ng update @angular/fire@next in an Angular 21 app stop with that message.
  • ng update @angular/fire@21.0.0-rc.1 in the same app gets past it.
  • ng update @angular/fire@21 answers Package specified by '@angular/fire@21' does not exist within the registry., so the bullet's example gives the full version. It can become @21 once 21.0.0 is published.
  • The guide's own command, ng update @angular/core@21 @angular/cli@21 @angular/fire@next, ran with a temporary Angular CLI 21.2.24 and completed.
  • On Node.js 22.23.2, ng update @angular/fire@next passes the Node.js check.

`ng update @angular/fire@next` can stop with "The Angular CLI requires
a minimum Node.js version of ..." on a Node.js version that Angular 21
supports. `ng update` runs with the newest Angular CLI when the first
@angular/ package in the command has no version number, and that CLI
requires a newer Node.js than Angular 21 does.

The example gives the full release-candidate version because
`@angular/fire@21` matches nothing until 21.0.0 is published.

Fixes angular#3786
@armando-navarro armando-navarro added bump: patch Size of the change: a fix or docs change that reaches users comp: docs Documentation. type: chore Maintenance with no user-facing behavior change. labels Oct 2, 2026

@tyler-reitz tyler-reitz left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving. The mechanism checks out against the CLI 21 source: getCLIUpdateRunnerVersion takes the first package matching /^@(?:angular|nguniversal)\//, which @angular/fire does, then falls back to latest when semver.parse cannot read a major. So the bullet is right, @next included.

One follow-up: the bullet hardcodes 21.0.0-rc.1, and nothing tracks switching it to @21 once 21.0.0 ships. Either file an issue for it or word it so it does not need editing later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bump: patch Size of the change: a fix or docs change that reaches users comp: docs Documentation. type: chore Maintenance with no user-facing behavior change.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The upgrade guide does not cover ng update stopping on a Node.js version message

2 participants