Feature request: using multiple firebase.json

[wneel]

Feature Request: Support multiple firebase.json configurations

Summary

Allow developers to use different firebase.json files based on environment (e.g., firebase.dev.json, firebase.prod.json) without relying on external scripts or manual file switching.

Use Case

In many projects, environments like development, staging, and production require different Firebase configurations (hosting targets, rewrites, public directories, etc). Currently, developers must:

• Use custom scripts to copy/rename firebase.json
• Maintain complex conditional logic within a single firebase.json
• Avoid committing generated files to version control

This setup is error-prone, difficult to scale, and breaks clean Git workflows.

Proposed Solution

Allow CLI commands to accept a flag or environment-based resolution. e.g:

firebase deploy --config firebase.prod.json

Alternatively, support automatic resolution based on an environment variable or project alias:

FIREBASE_ENV=prod firebase deploy

The CLI could then look for firebase.prod.json or similar.

Benefits

• Cleaner project organization
• Better Git integration
• No need for external scripting or file generation
• Aligns with common multi-environment practices in modern development