Install azurite with Homebrew, Nix

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• azurite
• azurite-blob
• azurite-queue
• azurite-table

Project history

Azurite began as a Node.js-based Azure Storage emulator and evolved through a legacy JavaScript V2 line into Azurite V3. The official README explains that V3 uses a TypeScript architecture and a server code generator aligned with Azure Storage swagger, replacing more manually maintained V2 code.

Microsoft Learn positions Azurite as the local emulator for Azure Storage development. The README documents separate `azurite`, `azurite-blob`, `azurite-queue`, and `azurite-table` commands, plus npm, Docker, Visual Studio Code, NuGet, and Visual Studio installation paths.

Adoption history

Azurite adoption tracks the growth of local-first cloud development. Azure developers use it in test suites, sample apps, CI jobs, and demos where real cloud storage would be slower, costlier, or harder to reset.

Package-manager adoption is narrower than Azure CLI but important: the input package facts list Homebrew and Nix packages, while the official README also highlights npm and Docker as mainstream installation routes.

How it is used

Common usage is simply `azurite` from a project directory, or service-specific commands such as `azurite-blob -l path/to/workspace`. The storage workspace defaults to the current working directory when `--location` is omitted; options control host, ports, debug logs, HTTPS certificates, OAuth behavior, and in-memory persistence.

There is no single user-level config file or credentials file documented for the CLI. Local storage state lives in the selected workspace, and custom accounts or keys can be supplied through environment variables or connection strings.

Why package nerds care

For package nerds, Azurite is a useful example of a cloud emulator packaged as a developer service, not just a command. It brings Node.js runtime expectations, multiple executables, long-lived local state, ports, Docker parity, and API-version compatibility into the package story.

It also replaced older Azure Storage Emulator workflows that were more Windows-centered, making Homebrew/Nix packaging matter for macOS and Linux developers building Azure-backed apps.

Timeline

• 2018: Azure/Azurite GitHub Releases include V2 releases.
• 2019: Azurite V3 preview introduces the TypeScript and generated-server architecture.
• 2020s: Azurite V3 supports Blob, Queue, and Table preview endpoints and is documented across Microsoft Learn, npm, Docker, and editor workflows.

Related projects

• Azure Storage Emulator was the older local emulator lineage for Azure Storage scenarios.
• Azure Storage SDKs and Storage Explorer are common clients pointed at Azurite.
• Azurite's generated-server architecture follows Azure Storage REST API swagger.

Sources

• Azure/Azurite README and releases
• Microsoft Learn Azurite docs
• source_facts.package-manager