[armando-navarro]

Checklist

• Issue number for this PR: Move Schematic dependencies to peerDependencies or devDependencies #3694 (required)
• Docs included?: Yes. A "Fewer build-time packages" section in docs/version-22-upgrade.md.
• Test units included?: No new specs. The build gains a check that fails when a deploy bundle requires a package the manifest does not declare, and the existing suite passes (385 node specs, 0 failures).
• In a clean directory, yarn install, yarn test run successfully?: yes, with npm (npm ci, npm run build, npm run build:jasmine && npm run test:node)

Description

Fixes #3694.

The published manifest declared five build-time packages that only the schematics and the ng deploy builder use: @angular-devkit/architect, @angular-devkit/core, @angular-devkit/schematics, @schematics/angular and jsonc-parser. After this change it declares one.

What changes

• @angular-devkit/schematics, @angular-devkit/core and @schematics/angular leave dependencies.
• jsonc-parser is bundled into the schematics (an esbuild alias to its ESM entry, since its UMD main cannot be bundled). Of the five, it was the one the schematics had to resolve on their own.
• @angular-devkit/architect stays declared.
• The deploy bundles stop requiring the schematic packages: builder.ts imported a .firebaserc helper from utils.ts, whose module-level imports esbuild kept, and actions.ts threw SchematicsException where Error prints the same message.
• The build now fails if a deploy bundle requires any package the manifest does not declare.

Why the three can leave and architect cannot

• The Angular CLI runs the schematics of packages installed under node_modules/@angular/, this one included, through its own module loader (schematic-engine-host.js).
• That loader supplies @angular-devkit/* and @schematics/* from the CLI's own copy and falls back to its copy of @angular-devkit/core.
• @angular/cdk, @angular/material, @angular/ssr and @angular/localize ship the same way.
• The architect host loads the deploy builder with a plain require, outside that loader, so the builder must find @angular-devkit/architect on its own.

What was measured

On fresh Angular 22 apps:

• With a build of this commit: ng add and the deploy builder under Yarn Plug'n'Play and under pnpm 9 with hoist=false, and the full ng add @angular/fire command through a local registry on npm 11.
• With the same change built before feat(deploy): deprecate deploying server-side rendering to Cloud Functions #3803 merged: ng add and the deploy builder on yarn 1, yarn 4 (both linkers), pnpm 9 in five layouts and pnpm 10, and the ng update migration on npm 11 and Yarn Plug'n'Play.
• A production install of a CLI app lists 112 packages instead of 136 (npm ci --omit=dev, then npm ls --omit=dev), and @schematics/angular with its oxc-parser dependency leaves it.

Compatibility

Not a breaking change.

• The Angular CLI depends on all five at exact versions, so a CLI or Nx workspace's development install does not change.
• Runners other than the Angular CLI (Nx, the devkit's own schematics command) have no module loader of their own and resolve these packages from the workspace. Nx's Angular template declares the three at the workspace root, and nx g @angular/fire:ng-add and nx run <project>:deploy reach the same points as under the CLI on pnpm's default layout.
• On pnpm with hoist=false, a locally installed schematics command needs the workspace root to declare @angular-devkit/schematics, @angular-devkit/core and @schematics/angular.

Relation to #3746

• Its fix, fix(schematics): declare the runtime dependencies the schematics bundle requires #3747, declared three of these packages on the expectation that pnpm's default layout does not resolve undeclared packages.
• Installs on pnpm 9 and 10 showed it does, through the hidden hoist directory node_modules/.pnpm/node_modules.
• Yarn Plug'n'Play, which does not, is covered by the CLI's loader for the schematics and by the declared architect for the builder.

Refs #3746

[tyler-reitz]

One follow-up: the body says the upgrade-guide note lands with docs/version-22-upgrade.md from #3805, but #3805 merged without it. Nothing documents yet that on pnpm with hoist=false, a locally installed schematics command needs @angular-devkit/schematics, @angular-devkit/core and @schematics/angular declared at the workspace root. Worth adding to that guide in a follow-up.

[armando-navarro]

I added the missing upgrade-guide note to this PR (78a08eb). It's a new "Fewer build-time packages" section at the end of docs/version-22-upgrade.md. It says which three packages @angular/fire no longer installs, and that running the schematics with the schematics command on pnpm with hoist=false needs them declared at the workspace root. I also changed the description's "Docs included?" line to say the guide is updated.