docs: cover ng update stopping on a Node.js version message - #3788
Merged
armando-navarro merged 4 commits intoOct 5, 2026
Merged
armando-navarro merged 4 commits into
armando-navarro merged 4 commits into
Conversation
`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
added
bump: patch
tyler-reitz
approved these changes
Oct 2, 2026
tyler-reitz
left a comment
tyler-reitz
left a comment
Collaborator
There was a problem hiding this comment.
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.
`ng update @angular/fire@21` matches nothing until 21.0.0 is published, so the note gave only the release-candidate form and would have needed an edit at the release. It now gives both.
Collaborator
Author
|
I reworded things in a follow-up commit, so the bullet mentions both forms, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3786
Adds a bullet under "Other notes" in
docs/version-21-upgrade.mdfor readers whoseng updatestops withThe 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/fireandng update @angular/fire@nextin an Angular 21 app stop with that message.ng update @angular/fire@21.0.0-rc.1in the same app gets past it.ng update @angular/fire@21answersPackage specified by '@angular/fire@21' does not exist within the registry., so the bullet's example gives the full version. It can become@21once21.0.0is published.ng update @angular/core@21 @angular/cli@21 @angular/fire@next, ran with a temporary Angular CLI 21.2.24 and completed.ng update @angular/fire@nextpasses the Node.js check.