firebase-dynamic-ports-setup

Name: firebase-dynamic-ports-setup
Availability: InStock
Author: ajelinek

Generate per-developer Firebase emulator port mappings and configs from ports.json.

Updated Apr 17, 2026

Search Tags:#automation #firebase #emulators #port-management #dev-environments #per-user #port-isolation

Ready to run

npx skills add https://github.com/ajelinek/skills-stash --skill firebase-dynamic-ports-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: firebase-dynamic-ports-setup
Source: https://github.com/ajelinek/skills-stash/tree/main/firebase-dynamic-ports-setup
Command: npx skills add https://github.com/ajelinek/skills-stash --skill firebase-dynamic-ports-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves port conflicts that occur when several developers run Firebase emulators on the same machine by generating per-developer port mappings and consistent configurations.

Core Features & Use Cases

Per-developer port isolation by prefixing base ports with an instance number (1–9).
Automated config generation: firebase.local.json and .env from ports.json to keep setup repeatable.
Conditional Functions emulator support based on project structure to avoid startup errors when no functions/ directory exists.
Reproducible onboarding, collaboration, and CI workflows with a shared, instance-specific setup.
Seamless integration with test runners and tooling via generated environment variables.

Quick Start

Run the setup script to configure per-developer ports and generate the necessary emulator config for your chosen instance.

Frequently Asked Questions about firebase-dynamic-ports-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent Firebase emulator port conflicts when multiple developers share the same host?▼

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.

How do I automatically configure Firebase emulator ports for a new developer instance?▼

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.

Does the Firebase emulator setup automatically include the Functions emulator?▼

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.

Can I use per-developer Firebase emulator configurations in CI workflows?▼

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.

What files do I need to set up isolated Firebase emulator environments?▼

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.