tailwindcss.cli 4.2.1

A dotnet tool to install the tailwindcss cli for windows (x64), macos (x64 and arm64) and linux (x64 and arm64).

This repository and the published wrapper tool now target .NET 10. Building from source requires the .NET 10 SDK, and running the wrapper requires a .NET 10 runtime.

Installation

Global install

dotnet tool install --global tailwindcss.cli

Once installed, tailwindcss should now be added to the path and invokable in your command prompts or terminals.

If the .NET 10 runtime is not installed, the wrapper will not start.

Note: on macos when using the default terminal zsh, globally installed tools will not be found. They will be found however if you use a bash shell.

To add globally installed tools to your zsh profile, edit ~/.zshrc and add the following line:

export PATH=$HOME/.dotnet/tools:$PATH

See: https://github.com/dotnet/sdk/issues/9415 for more information.

Local install

dotnet tool install tailwindcss.cli

Once installed, dotnet tailwindcss should now be invokable in your command prompts or terminals.

Installing specific versions

# global installs
dotnet tool install tailwindcss.cli --version 3.0.10 --global

# local installs
dotnet tool install tailwindcss.cli --version 3.0.10

Upgrading installations

# global installs
dotnet tool update tailwindcss.cli --version 3.0.10 --global

# local installs
dotnet tool update tailwindcss.cli --version 3.0.11

Uninstallation

# global installs
dotnet tool uninstall tailwindcss.cli --global

# local installs
dotnet tool uninstall tailwindcss.cli

GitHub Actions auto-sync

This repository now includes a GitHub Actions workflow at .github/workflows/sync-missing-packages.yml that:

• discovers stable upstream Tailwind CSS releases with the full runtime asset set
• compares each version against the wrapper package plus all platform packages on NuGet
• only publishes the missing package/version combinations

The workflow runs on a daily schedule and also supports manual workflow_dispatch runs with:

• dry_run: detect only, no NuGet publish
• version: optionally restrict the run to one stable Tailwind version such as 4.2.2

Publishing runs require a repository secret named NUGET_API_KEY.

Sync commands

You can run the same detection and sync flow locally:

# detect missing packages only
./build.sh DetectMissing --DryRun true

# detect missing packages for one version only
./build.sh DetectMissing --SpecificVersion 4.2.2 --DryRun true

# publish missing packages
./build.sh SyncMissing --NugetApiKey <key>

# publish missing packages for one version only
./build.sh SyncMissing --SpecificVersion 4.2.2 --NugetApiKey <key>

Every run writes a machine-readable summary to artifacts/package-sync-report.json.

Bootstrap process

On initial run, there is a bootstrap process to download the platform specific tailwindcss cli binary to be used. e.g.:

PS C:\Users\Duane> tailwindcss
Running on windows-x64, downloading tailwindcss cli v3.0.23 using nuget...
Package found in repository nuget.org: https://api.nuget.org/v3/index.json
Downloaded package tailwindcss.cli.windows.x64 v3.0.23 from nuget.org.
Extracting tailwindcss cli for windows-x64...

tailwindcss v3.0.23

Usage:
   tailwindcss [--input input.css] [--output output.css] [--watch] [options...]
   tailwindcss init [--full] [--postcss] [options...]
...