mirror of
https://github.com/tailwindlabs/tailwindcss.git
synced 2025-12-08 21:36:08 +00:00
f63b4531f5
* add nesting plugin * rename @tailwindcss/nesting to tailwindcss/nesting * ignore the built `nesting` plugin * add a postcss7 compat version * include `nesting` plugin when publishing * add `build-plugins` script This will allow us to keep the plugins in their dedicated folders + tests + postcss7 compatibility files. However, when we copy over the plugins to the root. For example `plugins/nesting/` -> `nesting/` we skip files like `.test.js` and `.postcss7.js`. * build plugins when running `prepublishOnly` * improve compat mode We will use a glob so that we can move all *.postcss7.* files to just *.* likewise we will also backup to *.* to *.postcss8.* for restoring purposes. Concrete example: - Current state: - index.js // PostCSS 8 implementation - index.postcss7.js // PostCSS 7 implementation - Run "compat" - index.js // PostCSS 7 implementation - index.postcss7.js // PostCSS 7 implementation - index.postcss8.js // PostCSS 8 implementation (Backup of original) - Run "compat:restore" - index.js // PostCSS 8 implementation - index.postcss7.js // PostCSS 7 implementation - X index.postcss8.js // PostCSS 8 implementation (Removed) * Update README.md * ensure we `npm install` before publishing Co-authored-by: Adam Wathan <adam.wathan@gmail.com>
43 lines
1.6 KiB
Markdown
43 lines
1.6 KiB
Markdown
# tailwindcss/nesting
|
|
|
|
This is a PostCSS plugin that wraps [postcss-nested](https://github.com/postcss/postcss-nested) or [postcss-nesting](https://github.com/jonathantneal/postcss-nesting) and acts as a compatibility layer to make sure your nesting plugin of choice properly understands Tailwind's custom syntax like `@apply` and `@screen`.
|
|
|
|
Add it to your PostCSS configuration, somewhere before Tailwind itself:
|
|
|
|
```js
|
|
// postcss.config.js
|
|
module.exports = {
|
|
plugins: [
|
|
require('postcss-import'),
|
|
require('tailwindcss/nesting'),
|
|
require('tailwindcss'),
|
|
require('autoprefixer'),
|
|
]
|
|
}
|
|
```
|
|
|
|
By default, it uses the [postcss-nested](https://github.com/postcss/postcss-nested) plugin under the hood, which uses a Sass-like syntax and is the plugin that powers nesting support in the [Tailwind CSS plugin API](https://tailwindcss.com/docs/plugins#css-in-js-syntax).
|
|
|
|
If you'd rather use [postcss-nesting](https://github.com/jonathantneal/postcss-nesting) (which is based on the work-in-progress [CSS Nesting](https://drafts.csswg.org/css-nesting-1/) specification), first install the plugin alongside:
|
|
|
|
```shell
|
|
npm install postcss-nesting
|
|
```
|
|
|
|
Then pass the plugin itself as an argument to `tailwindcss/nesting` in your PostCSS configuration:
|
|
|
|
```js
|
|
// postcss.config.js
|
|
module.exports = {
|
|
plugins: [
|
|
require('postcss-import'),
|
|
require('tailwindcss/nesting')(require('postcss-nesting')),
|
|
require('tailwindcss'),
|
|
require('autoprefixer'),
|
|
]
|
|
}
|
|
```
|
|
|
|
This can also be helpful if for whatever reason you need to use a very specific version of `postcss-nested` and want to override the version we bundle with `tailwindcss/nesting` itself.
|
|
|