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

FIREBASE_AUTH_EMULATOR_HOST affects all initailized apps, unlike other emulator env var

オープン
  • 何か問題がありますか？
#2,948 コメント 3 件 リアクション 1 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@lahirumaramba がすでに取り組んでいます。

2025年7月7日 から。

  • #3080 @daytonmux による — マージ済み

評価

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

説明

help wanted type: feature request

When initializing Firebase Admin to use the emulator, it's required to set the env var FIREBASE_AUTH_EMULATOR_HOST prior to calling initializeApp. This works fine, however, the way this value is used internally has a significant problem: The env var is consulted every time an API call is made. This makes it impossible to have two initialized apps in one process (for example, one pointing to the cloud project, and the other to the emulator.

The relevant code in this repo:

https://github.com/firebase/firebase-admin-node/blob/26b884f70300ef8e3213dfbbd72351ce7f68c695/src/auth/auth-api-request.ts#L2313-L2323

useEmulator is used whenever an API call is made, which affects all applications. So, one application cannot simply set the env var while another unsets it. What's especially confusing about this behavior is that the other env vars don't work like this at all. I can set the var only when needed prior to init, then unset it later to initialize another app.

For example, this works for Firestore and Storage, but not for Auth:

// Initializing an app for remote cloud project access

export const remoteApp = initializeApp(options, "remote")
export const remoteAuth = getAuth(remoteApp)
export const remoteFirestore = getFirestore(remoteApp)
export const remoteStorage = getStorage(remoteApp)

// Initializing a second app for local emulator access

process.env.FIREBASE_AUTH_EMULATOR_HOST="127.0.0.1:9099"
process.env.FIRESTORE_EMULATOR_HOST = "localhost:8080"
process.env.FIREBASE_STORAGE_EMULATOR_HOST = "127.0.0.1:9199"
export const localApp = initializeApp(options, "local")
export const localAuth = getAuth(localApp)
export const localFirestore = getFirestore(localApp)
export const localStorage = getStorage(localApp)
delete process.env.FIREBASE_AUTH_EMULATOR_HOST
delete process.env.FIRESTORE_EMULATOR_HOST
delete process.env.FIREBASE_STORAGE_EMULATOR_HOST

Deleting FIREBASE_AUTH_EMULATOR_HOST here causes the app for the local emulator to instead use the remote service. However, not deleting it causes the remote app to use the local emulator. Again, Firestore and Storage don't have this problem.

As of now, I can't find a way to use emulator auth and remote auth in the same project. It would be great if the admin SDK would take the value of FIREBASE_AUTH_EMULATOR_HOST just once at the time of init, store it, and use it later so that var can be deleted afterward. Or even better, initializeApp could directly take emulator configs as input instead of relying solely on env vars that affect the entire process globally.

See also this comment in another issue: https://github.com/firebase/firebase-admin-node/issues/776#issuecomment-1781154086

主要言語
TypeScript
スター
1.8k
フォーク
422
平均マージ
2日 4時間
マージ済み PR（30日）
18

環境構築

はじめの一歩

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

firebase/firebase-admin-node のほかの issue

firebase/firebase-admin-node の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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