A local-first web UI for the Firebase Emulator Suite, providing data viewers, editors, and logs for Firebase services during development.
Firebase Emulator UI is a web interface that provides a visual dashboard for the Firebase Emulator Suite, allowing developers to interact with local emulators of Firebase services like Realtime Database and Cloud Firestore. It enables data viewing, editing, and log inspection during development without needing a live Firebase project.
Firebase developers who use the Firebase Emulator Suite for local testing and want a graphical interface to manage emulated data and logs.
It offers a centralized, intuitive UI that simplifies working with Firebase emulators, reducing the need for command-line interactions and accelerating development cycles with real-time data manipulation and debugging tools.
A local-first UI for Firebase Emulator Suite.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically starts with the Firebase Emulator Suite via the CLI, requiring no separate UI setup for basic use, as noted in the README's usage section.
Provides web-based viewers and editors for Realtime Database and Cloud Firestore emulators, enabling direct data inspection and modification without CLI commands.
Includes a logs viewer with powerful filtering capabilities, aiding in debugging by isolating specific emulator events during development.
Operates entirely offline with local emulators, ensuring fast, secure development without internet connection or production data risks.
Setting up the development environment requires cloning the repo, installing dependencies, and using specific 'firebase emulators:exec' commands, which can be intricate and error-prone.
Only supports Firebase emulators, making it irrelevant for projects using other cloud providers or custom local backends beyond Firebase's services.
Development uses port 5173 while production defaults to 4000, and test setups can encounter port conflicts, as mentioned in the README's testing section.