GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — docs: cover ng update stopping on a Node.js version message by armando-navarro · Pull Request #3788 · angular/angularfire

Conversation

@armando-navarro

@armando-navarro armando-navarro commented Oct 2, 2026

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/[email protected] 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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@armando-navarro
docs: cover ng update stopping on a Node.js version message
e6be22b 
`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 requested a review from tyler-reitz October 2, 2026 18:54
@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 approved these changes Oct 2, 2026
View reviewed changes

@tyler-reitz tyler-reitz left a comment

Copy link
Copy Markdown
Collaborator

There was a problem hiding this comment.

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@armando-navarro
docs: name both ng update forms in the Node.js version note
545a0f9 
`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.
@armando-navarro

armando-navarro commented Oct 5, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Collaborator Author

I reworded things in a follow-up commit, so the bullet mentions both forms, @21.0.0-rc.1 for the release candidate and @21 once 21.0.0 is published, and needs no edit at the release.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
armando-navarro added 2 commits October 4, 2026 17:19
@armando-navarro
Merge branch 'main' into b14-upgrade-guide-node-version
97e0357
@armando-navarro
Merge branch 'main' into b14-upgrade-guide-node-version
13cb01b
@armando-navarro
armando-navarro enabled auto-merge (squash) October 5, 2026 00:31
@armando-navarro
armando-navarro merged commit 110dac1 into angular:main Oct 5, 2026
24 checks passed

Uh oh!

There was an error while loading. Please reload this page.
@armando-navarro armando-navarro added this to the 21.0.0-rc.2 milestone Oct 5, 2026
@armando-navarro
armando-navarro deleted the b14-upgrade-guide-node-version branch October 5, 2026 03:43
This was referenced Oct 23, 2026
docs: describe AngularFire 21 as released, not as a release candidate #3813
Merged
docs: describe AngularFire 21 as released, not as a release candidate (main) #3814
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@tyler-reitz tyler-reitz tyler-reitz approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

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

Milestone

21.0.0-rc.2

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

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@armando-navarro @tyler-reitz
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.