2024-03-06 14:49:31 +01:00
< p align = "center" >
< a href = "https://tailwindcss.com" target = "_blank" >
< picture >
< source media = "(prefers-color-scheme: dark)" srcset = "https://raw.githubusercontent.com/tailwindlabs/tailwindcss/HEAD/.github/logo-dark.svg" >
< source media = "(prefers-color-scheme: light)" srcset = "https://raw.githubusercontent.com/tailwindlabs/tailwindcss/HEAD/.github/logo-light.svg" >
< img alt = "Tailwind CSS" src = "https://raw.githubusercontent.com/tailwindlabs/tailwindcss/HEAD/.github/logo-light.svg" width = "350" height = "70" style = "max-width: 100%;" >
< / picture >
< / a >
< / p >
< p align = "center" >
A utility-first CSS framework for rapidly building custom user interfaces.
< / p >
< p align = "center" >
< a href = "https://github.com/tailwindlabs/tailwindcss/actions" > < img src = "https://img.shields.io/github/actions/workflow/status/tailwindlabs/tailwindcss/ci.yml?branch=next" alt = "Build Status" > < / a >
< a href = "https://www.npmjs.com/package/tailwindcss" > < img src = "https://img.shields.io/npm/dt/tailwindcss.svg" alt = "Total Downloads" > < / a >
2026-02-08 05:56:38 +05:30
< a href = "https://github.com/tailwindlabs/tailwindcss/releases" > < img src = "https://img.shields.io/npm/v/tailwindcss.svg" alt = "Latest Release" > < / a >
< a href = "https://github.com/tailwindlabs/tailwindcss/blob/main/LICENSE" > < img src = "https://img.shields.io/npm/l/tailwindcss.svg" alt = "License" > < / a >
2024-03-06 14:49:31 +01:00
< / p >
---
## Documentation
For full documentation, visit [tailwindcss.com ](https://tailwindcss.com ).
## Community
2025-07-02 22:49:47 +02:00
For help, discussion about best practices, or feature ideas:
2024-03-06 14:49:31 +01:00
2026-02-08 05:56:38 +05:30
[Discuss Tailwind CSS on GitHub ](https://github.com/tailwindlabs/tailwindcss/discussions )
2024-03-06 14:49:31 +01:00
## Contributing
2026-02-08 05:56:38 +05:30
If you're interested in contributing to Tailwind CSS, please read our [contributing docs ](https://github.com/tailwindlabs/tailwindcss/blob/main/.github/CONTRIBUTING.md ) **before submitting a pull request** .
2025-09-18 13:00:35 -04:00
---
## `@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:
```js
Add @tailwindcss/webpack loader for Tailwind CSS v4 (#19610)
## Summary
This PR adds a new `@tailwindcss/webpack` package that provides a
dedicated webpack loader for Tailwind CSS v4. This loader works with
both standard webpack and Turbopack's webpack loader compatibility
layer.
### Why a dedicated loader?
The current webpack integration uses `postcss-loader` +
`@tailwindcss/postcss`. While this works, a dedicated loader:
- **Eliminates PostCSS as a middleman** - works directly with CSS
strings (no AST conversions)
- **Simpler and more efficient** - follows the same pattern as
`@tailwindcss/vite`
- **Better for Turbopack** - gives direct control over dependency
reporting via webpack's loader API
### How it works
The loader mirrors the Vite plugin's approach:
1. Uses `compile()` from `@tailwindcss/node` to parse CSS and resolve
`@apply` directives
2. Uses `Scanner` from `@tailwindcss/oxide` to scan content files for
utility candidates
3. Reports dependencies via `this.addDependency()` and
`this.addContextDependency()`
4. Optionally optimizes output with Lightning CSS
### Usage
```javascript
// webpack.config.js
module.exports = {
module: {
rules: [
{
test: /.css$/i,
use: [
MiniCssExtractPlugin.loader,
'css-loader',
'@tailwindcss/webpack', // No PostCSS needed!
],
},
],
},
}
```
### Options
- `base` - The base directory to scan for class candidates (defaults to
`process.cwd()`)
- `optimize` - Whether to optimize/minify the output CSS (defaults to
`true` in production)
### Files added
- `packages/@tailwindcss-webpack/` - New package
- `src/index.ts` - Main loader implementation
- `src/index.cts` - CommonJS entry point for webpack compatibility
- `package.json`, `tsconfig.json`, `tsup.config.ts`, `README.md`
- `integrations/webpack/loader.test.ts` - Integration tests
- `integrations/utils.ts` - Added webpack override for transitive
dependencies
### Test plan
- [x] Build test - verifies basic compilation
- [x] Watch test - verifies HMR when adding new Tailwind classes
- [x] `@apply` test - verifies `@apply` directives work correctly
- [x] Optimization test - verifies minification works
---------
Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2026-01-29 15:16:31 +01:00
import tailwindcss from '@tailwindcss/postcss '
2025-09-18 13:00:35 -04:00
export default {
Add @tailwindcss/webpack loader for Tailwind CSS v4 (#19610)
## Summary
This PR adds a new `@tailwindcss/webpack` package that provides a
dedicated webpack loader for Tailwind CSS v4. This loader works with
both standard webpack and Turbopack's webpack loader compatibility
layer.
### Why a dedicated loader?
The current webpack integration uses `postcss-loader` +
`@tailwindcss/postcss`. While this works, a dedicated loader:
- **Eliminates PostCSS as a middleman** - works directly with CSS
strings (no AST conversions)
- **Simpler and more efficient** - follows the same pattern as
`@tailwindcss/vite`
- **Better for Turbopack** - gives direct control over dependency
reporting via webpack's loader API
### How it works
The loader mirrors the Vite plugin's approach:
1. Uses `compile()` from `@tailwindcss/node` to parse CSS and resolve
`@apply` directives
2. Uses `Scanner` from `@tailwindcss/oxide` to scan content files for
utility candidates
3. Reports dependencies via `this.addDependency()` and
`this.addContextDependency()`
4. Optionally optimizes output with Lightning CSS
### Usage
```javascript
// webpack.config.js
module.exports = {
module: {
rules: [
{
test: /.css$/i,
use: [
MiniCssExtractPlugin.loader,
'css-loader',
'@tailwindcss/webpack', // No PostCSS needed!
],
},
],
},
}
```
### Options
- `base` - The base directory to scan for class candidates (defaults to
`process.cwd()`)
- `optimize` - Whether to optimize/minify the output CSS (defaults to
`true` in production)
### Files added
- `packages/@tailwindcss-webpack/` - New package
- `src/index.ts` - Main loader implementation
- `src/index.cts` - CommonJS entry point for webpack compatibility
- `package.json`, `tsconfig.json`, `tsup.config.ts`, `README.md`
- `integrations/webpack/loader.test.ts` - Integration tests
- `integrations/utils.ts` - Added webpack override for transitive
dependencies
### Test plan
- [x] Build test - verifies basic compilation
- [x] Watch test - verifies HMR when adding new Tailwind classes
- [x] `@apply` test - verifies `@apply` directives work correctly
- [x] Optimization test - verifies minification works
---------
Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2026-01-29 15:16:31 +01:00
plugins: [
tailwindcss({
base: path.resolve(__dirname, './path'),
}),
],
2025-09-18 13:00:35 -04:00
}
```
### 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:
```js
2025-09-29 15:59:54 +02:00
import tailwindcss from '@tailwindcss/postcss '
2025-09-18 13:00:35 -04:00
export default {
2025-09-29 15:59:54 +02:00
plugins: [
tailwindcss({
// Enable or disable Lightning CSS
optimize: false,
}),
],
2025-09-18 13:00:35 -04:00
}
```
It's also possible to keep Lightning CSS enabled but disable minification:
```js
2025-09-29 15:59:54 +02:00
import tailwindcss from '@tailwindcss/postcss '
2025-09-18 13:00:35 -04:00
export default {
2025-09-29 15:59:54 +02:00
plugins: [
tailwindcss({
optimize: { minify: false },
}),
],
2025-09-18 13:00:35 -04:00
}
```
### 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:
```js
2025-09-29 15:59:54 +02:00
import tailwindcss from '@tailwindcss/postcss '
2025-09-18 13:00:35 -04:00
export default {
2025-09-29 15:59:54 +02:00
plugins: [
tailwindcss({
// Disable `url(…)` rewriting
transformAssetUrls: false,
// Enable `url(…)` rewriting (the default)
transformAssetUrls: true,
}),
],
2025-09-18 13:00:35 -04:00
}
```
You may also pass options to `optimize` to enable Lighting CSS but prevent minification:
```js
2025-09-29 15:59:54 +02:00
import tailwindcss from '@tailwindcss/postcss '
2025-09-18 13:00:35 -04:00
export default {
2025-09-29 15:59:54 +02:00
plugins: [
tailwindcss({
// Enables Lightning CSS but disables minification
optimize: { minify: false },
}),
],
2025-09-18 13:00:35 -04:00
}
```