Firebase Emulator Suite - Commands & Configuration

Introduction

The Firebase Emulator Suite lets you run Firebase services on your computer. This helps you build and test your app safely without touching real data or spending money.

When you want to test your app's database changes without affecting live data.

When you need to develop authentication flows without creating real user accounts.

When you want to try Cloud Functions locally before deploying them.

When you want to simulate Firestore or Realtime Database behavior offline.

When you want to run integration tests that involve multiple Firebase services.

Config File - firebase.json

firebase.json

{
  "emulators": {
    "auth": {
      "port": 9099
    },
    "firestore": {
      "port": 8080
    },
    "functions": {
      "port": 5001
    },
    "ui": {
      "enabled": true,
      "port": 4000
    }
  }
}

This file configures which Firebase emulators to run and their ports.

auth: Runs the Authentication emulator on port 9099.

firestore: Runs the Firestore emulator on port 8080.

functions: Runs the Cloud Functions emulator on port 5001.

ui: Enables the Emulator Suite UI on port 4000 for easy management.

Commands

Starts all Firebase emulators defined in firebase.json so you can test your app locally.

Terminal

firebase emulators:start

Expected Output

i  emulators: Starting emulators: auth, firestore, functions, ui

✔  functions: Using node@16 from host.

✔  firestore: Firestore Emulator logging to firestore-debug.log

✔  auth: Authentication Emulator logging to auth-debug.log

✔  ui: Emulator UI logging to ui-debug.log

✔  All emulators started, it is now safe to connect your app.

Runs your Cloud Functions code locally in the emulator, then deploys only functions to Firebase if tests pass.

Terminal

firebase emulators:exec "firebase deploy --only functions"

Expected Output

i  emulators: Starting emulators: functions

✔  functions: Using node@16 from host.

✔  functions: Emulator started at http://localhost:5001

✔  functions: Deployment complete.

✔  All emulators stopped.

Stops all running Firebase emulators to free up your computer's resources.

Terminal

firebase emulators:stop

Expected Output

✔  All emulators stopped.

Key Concept

If you remember nothing else from this pattern, remember: The Firebase Emulator Suite lets you safely build and test your app locally without touching live data.

Common Mistakes

Trying to connect your app to the real Firebase services while the emulator is running.

Your app won't use the emulator and may change live data or fail if credentials differ.

Configure your app to connect to the local emulator endpoints during development.

Not defining the emulators and their ports in firebase.json before starting.

The emulator won't start or will use default ports that might conflict with other services.

Always set up firebase.json with the emulators you want and their ports.

Leaving emulators running after finishing development.

Emulators consume system resources and may cause port conflicts later.

Run 'firebase emulators:stop' to cleanly shut down all emulators.

Summary

Create a firebase.json file to configure which emulators to run and their ports.

Use 'firebase emulators:start' to launch all configured emulators for local testing.

Stop emulators with 'firebase emulators:stop' when done to free resources.

Practice

1. What is the main purpose of the Firebase Emulator Suite?

easy

A. To monitor live user data in real time

B. To deploy Firebase apps directly to production

C. To run Firebase services locally for safe app testing

D. To backup Firebase databases automatically

Solution

1. Step 1: Understand Firebase Emulator Suite role

   The Emulator Suite runs Firebase services on your computer, not on the cloud.

2. Step 2: Identify its main use

   It allows safe testing without affecting real data or users.

3. Final Answer:

   To run Firebase services locally for safe app testing -> Option C

4. Quick Check:

   Local testing = Safe app development [OK]

Hint: Emulator = local safe testing environment [OK]

Common Mistakes:

• Confusing emulator with live deployment
• Thinking it monitors real user data
• Assuming it backs up data automatically

2. Which command starts the Firebase Emulator Suite with Firestore and Authentication emulators only?

easy

A. firebase emulators:start --only firestore,auth

B. firebase start --emulators firestore auth

C. firebase emulators:run firestore auth

D. firebase launch --services firestore,auth

Solution

1. Step 1: Recall correct Firebase CLI syntax

   The command to start emulators uses 'firebase emulators:start' with '--only' to specify services.

2. Step 2: Match correct option

   firebase emulators:start --only firestore,auth uses the exact syntax: 'firebase emulators:start --only firestore,auth'. Others are invalid commands.

3. Final Answer:

   firebase emulators:start --only firestore,auth -> Option A

4. Quick Check:

   Correct CLI syntax = firebase emulators:start --only firestore,auth [OK]

Hint: Use 'firebase emulators:start --only' to pick services [OK]

Common Mistakes:

• Using 'firebase start' instead of 'firebase emulators:start'
• Omitting '--only' when selecting emulators
• Wrong command verbs like 'run' or 'launch'

3. Given this command: firebase emulators:start --only database, what will happen?

medium

A. The Authentication emulator will start alongside database

B. Only the Realtime Database emulator will start

C. The command will fail due to missing Firestore emulator

D. All Firebase emulators will start except database

Solution

1. Step 1: Analyze the command's '--only' flag

   The '--only database' means start only the Realtime Database emulator.

2. Step 2: Understand emulator behavior

   No other emulators start unless explicitly listed.

3. Final Answer:

   Only the Realtime Database emulator will start -> Option B

4. Quick Check:

   '--only database' = start database emulator only [OK]

Hint: '--only' limits emulators to listed services [OK]

Common Mistakes:

• Assuming all emulators start by default
• Thinking Firestore or Auth start automatically
• Believing command fails without Firestore

4. You run firebase emulators:start --only firestore,auth but get an error saying the port is in use. What should you do?

medium

A. Uninstall and reinstall Firebase CLI

B. Restart your computer to free all ports

C. Remove the '--only' flag and try again

D. Change the emulator ports in the firebase.json config file

Solution

1. Step 1: Understand port conflict cause

   Port in use means another app or emulator uses the same port number.

2. Step 2: Fix by changing ports in config

   Modify ports in firebase.json under 'emulators' section to unused ports.

3. Final Answer:

   Change the emulator ports in the firebase.json config file -> Option D

4. Quick Check:

   Port conflict fix = change ports [OK]

Hint: Edit firebase.json ports to avoid conflicts [OK]

Common Mistakes:

• Restarting computer without checking ports
• Removing '--only' does not fix port issues
• Reinstalling CLI unnecessarily

5. You want to test your app's Firestore rules locally and also simulate Authentication sign-in. Which setup is best?

hard

A. Run Firebase Emulator Suite with Firestore and Auth emulators, then connect your app to them

B. Use only Firestore emulator since Auth is not needed for rules testing

C. Test rules on live Firestore with test user accounts

D. Run Authentication emulator alone and skip Firestore emulator

Solution

1. Step 1: Identify testing needs

   You need Firestore emulator for rules and Auth emulator to simulate sign-in.

2. Step 2: Choose setup that covers both

   Running both emulators locally and connecting your app allows full safe testing.

3. Final Answer:

   Run Firebase Emulator Suite with Firestore and Auth emulators, then connect your app to them -> Option A

4. Quick Check:

   Test rules + auth = run both emulators [OK]

Hint: Run all needed emulators together for full local testing [OK]

Common Mistakes:

• Skipping Auth emulator when testing sign-in
• Testing rules on live data risking real users
• Running only one emulator when both needed