René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"firebase-tools peerDependency excludes v15 (the current major)","articleBody":"### Version info\n\n**Angular:** 21.2.x (any Angular 21)\n\n**Firebase:** 12.x\n\n**AngularFire:** 21.0.0-rc.0 (`@next`)\n\n**Other:** firebase-tools 15.x; npm / pnpm\n\n### How to reproduce these conditions\n\n**Steps to set up and reproduce**\n\n1. Install `@angular/fire@next` in a project that also has `firebase-tools@15` (the current major).\n2. The package manager emits an unmet/invalid optional-peer warning for `firebase-tools` (or an `ERESOLVE` under pnpm / `--strict-peer-deps`), because `@angular/fire` declares `\"firebase-tools\": \"^14.0.0\"`, which excludes 15.x.\n\nThis is a static package-metadata issue, reproducible directly from the published `@angular/fire` `package.json` — no Stackblitz needed.\n\n### Debug output\n\n```\nnpm warn ERESOLVE overriding peer dependency\nnpm warn Could not resolve dependency:\nnpm warn peerOptional firebase-tools@\"^14.0.0\" from @angular/fire@21.0.0-rc.0\n```\n\n### Expected behavior\n\nThe optional `firebase-tools` peer range includes the current firebase-tools major (15.x), so users on the current CLI get no spurious peer warning. The `ng add` runtime version check already only requires `\u003e= 14.0.0`, and the schematic runs fine on 15.x.\n\n### Actual behavior\n\n`@angular/fire`'s `peerDependencies.firebase-tools` is `^14.0.0`, excluding 15.x. This peer range has repeatedly fallen behind the firebase-tools release train (see #3237, #3238, #3479). Proposed fix: `^14.0.0 || ^15.0.0`.\n","author":{"url":"https://github.com/armando-navarro","@type":"Person","name":"armando-navarro"},"datePublished":"2026-07-07T22:15:23.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/3701/angularfire/issues/3701"}