Step 1 of docs/install-and-setup.md creates a project with npm create @angular@21 <project-name>. On npm older than 11.6 that command stops while installing packages:
npm error Cannot read properties of null (reading 'edgesOut')
✖ Package install failed, see above.
This is an npm bug, npm/cli#9787, and it happens before AngularFire is involved. Angular closed its own report of it, angular/angular-cli#34083, as an npm bug. A quickstart reader meets it anyway, because the newest Node.js 20 and 22 releases come with npm 10.
What I ran
A new Angular 21 project, on 2026-10-02:
- npm 10.8.2, 10.9.8, 10.9.9, 11.3.0 and 11.5.2 fail with the error above.
- npm 11.6.0, 11.19.0, 11.21.0 and 12.2.0 install.
- A failed run leaves the project folder behind, and running the command again into it fails with
A merge conflicted on path "/<project-name>/package.json".
Proposed change
One line under step 1 that names the error and says to run npm install -g npm@11, delete the leftover folder, and run the command again.
Step 1 of
docs/install-and-setup.mdcreates a project withnpm create @angular@21 <project-name>. On npm older than 11.6 that command stops while installing packages:This is an npm bug, npm/cli#9787, and it happens before AngularFire is involved. Angular closed its own report of it, angular/angular-cli#34083, as an npm bug. A quickstart reader meets it anyway, because the newest Node.js 20 and 22 releases come with npm 10.
What I ran
A new Angular 21 project, on 2026-10-02:
A merge conflicted on path "/<project-name>/package.json".Proposed change
One line under step 1 that names the error and says to run
npm install -g npm@11, delete the leftover folder, and run the command again.