The Nitro CLI ships in several flavors so you can pick whatever fits your environment best.

.NET tool

If you have the .NET SDK installed, you can install the CLI as a .NET tool.

Install as a local tool, scoped to a repository via a tool manifest. From the repository root:

dotnet new tool-manifest
dotnet tool install ChilliCream.Nitro.CommandLine

Local tools are restored with dotnet tool restore and invoked through dotnet tool run nitro (or dotnet nitro). Check the manifest (./.config/dotnet-tools.json) into source control so every collaborator uses the same version.

Or install globally:

dotnet tool install -g ChilliCream.Nitro.CommandLine

npm

The CLI is published to npm as @chillicream/nitro. For one-off invocations run it with npx. The @latest tag opts out of npm's local cache so each run pulls the newest release:

npx @chillicream/nitro@latest --version

Homebrew (macOS and Linux)

The CLI is available through the chillicream/tools tap:

brew tap chillicream/tools
brew install nitro-cli

To upgrade later:

brew update
brew upgrade nitro-cli

Pre-built binaries

Pre-built binaries for every supported OS and architecture are attached to each GitHub release.

Extract the archive and place the nitro binary somewhere on your PATH. The binaries are self-contained, no .NET SDK or runtime is required on the target machine.