Files
aphrody-dev f8a1923171 fix(aphrody): restore turbo build, drop unverified cargo/postcss changes, fix compileStream
- build is turbo again (oxide, all packages, .d.ts); fast-build.ts stays as
  build:fast, documented as a JS-only dev build, with the browser intellisense stub
- remove .cargo/config.toml (cargo has no linker-flavor key, rust-lld on macOS)
  and restore the upstream release profile (lto = true)
- revert the @tailwindcss/postcss candidate-hash cache and its duplicate
  compileStream/hashCandidates exports
- @tailwindcss/node compileStream: optional base/onDependency, no circular
  re-export from compile.ts, exported from index.cts, meaningful tests;
  drop the unused hashCandidates
- restore the v3 playground upgrade script (package.json was invalid JSON)
- test preload warns instead of silently skipping the snapshot serializer
2026-10-09 03:25:42 +02:00
..
2026-04-24 21:21:12 +02:00

Tailwind CSS

A utility-first CSS framework for rapidly building custom user interfaces.

Build Status Total Downloads Latest Release License


Documentation

For full documentation, visit tailwindcss.com.

Community

For help, discussion about best practices, or feature ideas:

Discuss Tailwind CSS on GitHub

Contributing

If you're interested in contributing to Tailwind CSS, please read our contributing docs before submitting a pull request.


@tailwindcss/postcss plugin API

Changing where the plugin searches for source files

You can use the base option (defaults to the current working directory) to change the directory in which the plugin searches for source files:

import tailwindcss from '@tailwindcss/postcss'

export default {
  plugins: [
    tailwindcss({
      base: path.resolve(__dirname, './path'),
    }),
  ],
}

Enabling or disabling Lightning CSS

By default, this plugin detects whether or not the CSS is being built for production by checking the NODE_ENV environment variable. When building for production Lightning CSS will be enabled otherwise it is disabled.

If you want to always enable or disable Lightning CSS the optimize option may be used:

import tailwindcss from '@tailwindcss/postcss'

export default {
  plugins: [
    tailwindcss({
      // Enable or disable Lightning CSS
      optimize: false,
    }),
  ],
}

It's also possible to keep Lightning CSS enabled but disable minification:

import tailwindcss from '@tailwindcss/postcss'

export default {
  plugins: [
    tailwindcss({
      optimize: { minify: false },
    }),
  ],
}

Enabling or disabling url(…) rewriting

Our PostCSS plugin can rewrite url(…)s for you since it also handles @import (no postcss-import is needed). This feature is enabled by default.

In some situations the bundler or framework you're using may provide this feature itself. In this case you can set transformAssetUrls to false to disable this feature:

import tailwindcss from '@tailwindcss/postcss'

export default {
  plugins: [
    tailwindcss({
      // Disable `url(…)` rewriting
      transformAssetUrls: false,

      // Enable `url(…)` rewriting (the default)
      transformAssetUrls: true,
    }),
  ],
}