使用 Homebrew, Nix, scoop 安装 tailwindcss

项目链接

• 主页
• 仓库

命令和别名

• tailwindcss

项目历史

Tailwind CSS grew out of the utility-first CSS movement and reached a stable 1.0 milestone before the 2.0 release. The official Tailwind CSS v2.0 announcement says v1.0 had been released almost exactly 18 months earlier and describes v2.0 as the framework's first major update, adding a new color palette, dark mode support, wider breakpoints, form styles, and other utility expansions.

Tailwind CSS v2.1 brought the Just-in-Time engine into core as an opt-in feature after the separate JIT preview, changing Tailwind from a mostly ahead-of-time utility generator into a faster on-demand compiler. Tailwind CSS v2.2 followed with a rewritten high-performance CLI, making the command-line package itself a first-class workflow.

Tailwind CSS v4.0 was announced as a ground-up rewrite optimized for performance and modern CSS. The v4 docs and blog emphasize CSS-first configuration with `@theme`, automatic content detection, built-in import handling, and first-party integration through `@tailwindcss/cli` and `@tailwindcss/vite`.

采用历史

Tailwind's adoption is visible in its packaging surface: npm is primary, but Homebrew, Nix, and Scoop package the CLI for users who want a system-level executable. The official README points users to tailwindcss.com for documentation and to GitHub Discussions for community support, while the docs provide framework-specific installation paths.

The framework also developed an ecosystem around editor support, Headless UI, Heroicons, Tailwind Plus, and Tailwind Play. For package-manager users, that ecosystem matters because Tailwind is often installed both as a project dependency and as an editor or CLI tool.

使用方式

Official CLI documentation installs `tailwindcss` and `@tailwindcss/cli`, imports `@import "tailwindcss";` in a CSS file, and runs `npx @tailwindcss/cli -i ./src/input.css -o ./src/output.css --watch`. Tailwind then scans templates for class names and generates the corresponding static CSS.

Current v4 customization is primarily CSS-driven through theme variables and directives. Legacy JavaScript configuration can still be loaded with `@config`, but the docs mark that path as compatibility for Tailwind CSS v3.x projects and note unsupported v4 options.

为什么软件包爱好者会关心

Tailwind CSS is package-nerd significant because it sits at the intersection of frontend build tooling, package-manager workflows, and editor tooling. It is commonly pulled through npm in projects but also packaged as a standalone CLI for Homebrew and other managers, making it a frequent test case for how JavaScript build tools are wrapped for system package ecosystems.

Its evolution from configuration-heavy JavaScript files toward CSS-first configuration and standalone CLI packages also tracks a broader packaging concern: reducing required toolchain assumptions while keeping fast incremental builds and framework integration.

时间线

• 2019: Tailwind CSS v1.0 stability milestone, referenced by the v2.0 announcement as almost exactly 18 months before v2.0.
• 2020: Tailwind CSS v2.0 released as the first major update.
• 2021: Tailwind CSS v2.1 merged the JIT engine into core.
• 2021: Tailwind CSS v2.2 introduced a rewritten high-performance CLI.
• 2025: Tailwind CSS v4.0 released as a ground-up rewrite with CSS-first configuration and modern web-platform features.

Related projects

• Related first-party projects include Tailwind CSS IntelliSense, Headless UI, Heroicons, Tailwind Play, and Tailwind Plus. The language server and IntelliSense extension are especially relevant to CLI/package culture because they package Tailwind's class knowledge for editors.

来源

• https://github.com/tailwindlabs/tailwindcss#readme
• https://tailwindcss.com/blog/tailwindcss-2-1
• https://tailwindcss.com/blog/tailwindcss-2-2
• https://tailwindcss.com/blog/tailwindcss-v2
• https://tailwindcss.com/blog/tailwindcss-v4
• https://tailwindcss.com/docs
• https://tailwindcss.com/docs/functions-and-directives
• https://tailwindcss.com/docs/installation/tailwind-cli