Firebase projects are created in the firebase web console, and then specified in your local workspace configurations as deployment targets in your .firebaserc file.
nx-firebase assumes a mapping of one @simondotm/nx-firebase:app to one firebase CLI project and one Firebase configuration file.
The first time you run nx g @simondotm/nx-firebase:app in an Nx workspace, it will generate a firebase configuration file called firebase.json in the workspace root. If you only use a single Firebase project in your Nx workspace, this will be all you need.
The Firebase CLI will use this configuration file by default, and in this scenario there's no need to pass the additional --config CLI option.
This plugin supports multiple Firebase Applications/Projects inside one Nx workspace.
If you run nx g @simondotm/nx-firebase:app in an Nx workspace that already has a firebase.json configuration file, it will generate a file called firebase.<appname>.json configuration in the Nx workspace root which can then be used with any Firebase CLI command by using the --config <config> CLI option.
Once your Nx Firebase application has been initially generated you are free to change the firebase configurations however you like.
The Firebase CLI usually warns you anyway if you try to deploy a feature that isn't yet enabled on your Firebase Project console.
When using multiple Firebase projects in a workspace, remember that there is only one .firebaserc file to contain aliases for all of your deployment targets.
You can add projects using firebase use --add as normal.
It's fine to add multiple Firebase projects to your workspace .firebaserc file, but it is important to remember to correctly switch between them using firebase use <alias> before any deployments!
You can ensure this is always the case for commands like nx deploy app etc. by adding --project <alias> to any firebase commands in your nx-firebase application's targets.
See also: Changing Firebase CLI Project
A common practice with Firebase is to generate different Firebase projects for each deployment environments (such as dev / staging / production etc.)
This can be manually achieved with nx-firebase by adding production configurations to the firebase target in your Nx firebase application project.json file eg.:
firebase: {
executor: 'nx:run-commands',
options: {
command: `firebase --config firebase.json --project your-dev-firebase-project`,
},
configurations: {
production: {
command: `firebase --config firebase.json --project your-prod-firebase-project`,
},
},
},
You can now run:
nx deploy my-firebase-appfor dev deploymentnx deploy my-firebase-app --prodfor production deployment
Note that your-dev-firebase-project and your-prod-firebase-project must exist as aliases in your .firebaserc file for this to work.