firebase-dynamic-ports-setup

To prevent Firebase emulator port conflicts on a shared host, generate per-developer port mappings by prefixing base ports from ports.json with a unique instance number (1–9). This creates isolated configurations for each developer running emulators locally.

To automatically configure Firebase emulator ports, run the setup script to apply an instance number to base ports and generate firebase.local.json and .env files. This provides consistent, per-developer emulator configurations without manual port editing.

The Firebase emulator setup conditionally includes the Functions emulator only if a functions/ directory exists in your project. This prevents startup errors when running emulator configurations for projects without Cloud Functions.

Yes, you can use per-developer Firebase emulator configurations in CI workflows and onboarding scenarios. The generated environment variables and instance-specific firebase.local.json files ensure reproducible setups across automated pipelines and local development.

To set up isolated Firebase emulator environments, you need a base ports.json file. The setup script reads this file to generate the final firebase.local.json and .env configurations with prefixed ports for each developer instance.