Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Six `firebase` entry points have no `@angular/fire` equivalent, so their exports are unreachable

オープン
#3,755 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

@armando-navarro がすでに取り組んでいます。

2026年8月31日 から。

評価

この issue はまだ評価されていません。

説明

comp: core type: feature
Summary

firebase 12.18.0 publishes 20 importable paths that are not compat. tools/build.ts re-exports 14 of them. Anything exported from the other six is unreachable through @angular/fire, so an app that needs it has to import from firebase directly and give up the Angular behavior AngularFire adds for that part of its code.

The six unreachable paths
  • firebase/firestore/pipelines
  • firebase/firestore/lite/pipelines
  • firebase/auth/cordova
  • firebase/auth/web-extension
  • firebase/installations
  • firebase/messaging/sw

The two pipelines paths are recent: firebase 12.4.0 publishes no path containing pipelines, and 12.8.0 publishes two. The other four exist in 12.4.0 and so have been unreachable for as long as that has been the version the package is built against.

Why this is separate from a wrapped module missing symbols

A missing symbol inside a path AngularFire already ships is fixed by re-running tools/build.ts, which regenerates that path's src/<module>/firebase.ts from the installed firebase and picks the new symbol up.

A missing path is not fixed that way, because there is nothing for the generator to regenerate. tools/build.ts only writes the firebase.ts file inside a directory that already exists, and the rest of that directory is written by hand. src/firestore/lite/ is 8 files and 269 lines, of which only firebase.ts is generated.

Things to consider

This is not a single mechanical change, and I do not think all six should be treated the same way:

  • Whether to ship each path at all. firebase/messaging/sw runs in a service worker and firebase/auth/cordova targets a platform Angular apps rarely use, so an Angular wrapper may not be the right home for either.
  • For each path that ships, every function in it has to be classified for wrapping, the same way the existing modules were.
  • The cost is per path, roughly six or seven hand-written files each, so this may be better done a path at a time than as one change.

If you are blocked on one of these specifically, saying which one and what you are trying to do would help order the work. firebase/firestore/pipelines is the one with a request already attached to it, in #3693.

主要言語
TypeScript
スター
7.8k
フォーク
2.2k
平均マージ
22時間 34分
マージ済み PR(30日)
4

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

angular/angularfire のほかの issue

angular/angularfire の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。