You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 6, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,8 @@ Add `@tailwindcss/jit` to your PostCSS configuration _(instead of `tailwindcss`)
42
42
}
43
43
```
44
44
45
+
> If you are using autoprefixer, make sure you are on the latest version using `npm install -D autoprefixer@latest`, there's a bug in older versions that makes it incompatible with this library.
46
+
45
47
Configure the `purge` option in your `tailwind.config.js` file with all of your template paths:
46
48
47
49
```js
@@ -118,7 +120,6 @@ There are a few items still on our todo list though that we are actively working
118
120
- The `important` option does not yet support selectors (like `#app`).
119
121
- Advanced PurgeCSS options like `safelist` aren't supported yet since we aren't actually using PurgeCSS. We'll add a way to safelist classes for sure though. For now, a `safelist.txt` file somewhere in your project with all the classes you want to safelist will work fine.
120
122
- You can only `@apply` classes that are part of core, generated by plugins, or defined within a `@layer` rule. You can't `@apply` arbitrary CSS classes that aren't defined within a `@layer` rule.
121
-
- Requires updating `autoprefixer` to the latest version using (`npm install -D autoprefixer@latest`). Does not support the latest `postcss-preset-env` due to `autoprefixer` version.
122
123
123
124
If you run into any other issues or find any bugs, please [open an issue](https://github.com/tailwindlabs/tailwindcss-jit/issues/new) so we can fix it.
0 commit comments