firebase-cli mit Homebrew, winget, scoop installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• firebase

Projektgeschichte

The firebase-tools GitHub repository was created in December 2013, during Firebase's early developer-platform era. The official README now describes it as both the Firebase Command Line Interface tools and the home of the official Firebase MCP Server.

Firebase CLI grew with the Firebase platform. Its README command list shows the tool expanding beyond Hosting deployment into project management, local emulators, App Distribution, Authentication, Realtime Database, Extensions, Firestore, Cloud Functions, Hosting, and Remote Config.

Adoptionsgeschichte

The primary installation path is npm: `npm install -g firebase-tools` provides the globally accessible `firebase` command. The official README also documents a standalone binary installer, which matters for users who want a dependency-light CLI outside a Node development environment.

Firebase CLI adoption is tied to Firebase project workflows. Developers use it locally for `firebase init`, `firebase login`, emulator startup, and deployment; teams use it in CI for deploys, project listing, and authenticated service-account or token-based automation.

Wie es verwendet wird

A typical workflow starts with `firebase login` and `firebase init`, which creates a `firebase.json` configuration file in the current project directory. Deployment commands then rely on that local project folder and configuration.

The CLI is also a local development surface. Commands such as `emulators:start`, `emulators:exec`, `serve`, and Functions shell support let developers test Firebase services before deploying to Google-hosted infrastructure.

Warum Paket-Nerds sich dafür interessieren

Firebase CLI is significant because it is a cloud product's operational surface packaged as a local developer tool. Installing one package gives a project its deploy command, emulator runner, auth setup, project selector, data import/export utility, and CI automation hook.

For package managers, it is also a Node-based CLI with standalone binary distribution, so it sits at the intersection of npm global installs, Homebrew-style desktop tooling, and vendor-managed cloud workflows.

Zeitleiste

• 2013: firebase-tools repository is created on GitHub.
• 2010s: npm global installation becomes the primary documented installation path for the `firebase` command.
• 2020s: CLI command surface includes local emulators, App Distribution, Extensions, Firestore, Functions, Hosting, and Remote Config workflows.
• 2026: Repository metadata and the README snapshot used for this enrichment show active maintenance and the addition of the official Firebase MCP Server in the same repository.

Related projects

• Firebase Hosting, Cloud Functions for Firebase, Realtime Database, Cloud Firestore, Authentication, Remote Config, App Distribution, Extensions, and the Emulator Suite are first-party services managed by the CLI.
• Node.js and npm are the primary runtime and package-manager path documented for installing firebase-tools.
• Google Cloud service-account credentials and Application Default Credentials are supported authentication paths for automation.

Quellen

• https://firebase.google.com/docs/cli
• https://github.com/firebase/firebase-tools
• https://raw.githubusercontent.com/firebase/firebase-tools/master/README.md
• https://api.github.com/repos/firebase/firebase-tools