Skip to content
This repository was archived by the owner on Apr 6, 2021. It is now read-only.

Commit 48be496

Browse files
authored
Update README.md
1 parent dd21450 commit 48be496

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

README.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,8 @@ Add `@tailwindcss/jit` to your PostCSS configuration _(instead of `tailwindcss`)
4242
}
4343
```
4444

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+
4547
Configure the `purge` option in your `tailwind.config.js` file with all of your template paths:
4648

4749
```js
@@ -118,7 +120,6 @@ There are a few items still on our todo list though that we are actively working
118120
- The `important` option does not yet support selectors (like `#app`).
119121
- 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.
120122
- 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.
122123

123124
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.
124125

0 commit comments

Comments
 (0)