From dd21450c87a4b3fa0ecff28dc990f72b52e742e3 Mon Sep 17 00:00:00 2001 From: Ido Shamun Date: Tue, 16 Mar 2021 11:10:01 +0200 Subject: [PATCH 1/3] Add autoprefixer known limitation to readme When I first tried to use the new compiler, I bumped into this error: `Maximum call stack size exceeded` Thanks to #29, I noticed that I must use the latest version of the `autoprefixer`, which indeed fixed this issue. Unfortunately, it can't be found anywhere in the docs. --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 6334a67..dbc9224 100644 --- a/README.md +++ b/README.md @@ -118,6 +118,7 @@ There are a few items still on our todo list though that we are actively working - The `important` option does not yet support selectors (like `#app`). - 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. - 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. +- 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. 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. From 48be496286b0a262afb6f7569fd79bb65188c6a3 Mon Sep 17 00:00:00 2001 From: Adam Wathan Date: Tue, 16 Mar 2021 11:16:32 -0400 Subject: [PATCH 2/3] Update README.md --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index dbc9224..767db93 100644 --- a/README.md +++ b/README.md @@ -42,6 +42,8 @@ Add `@tailwindcss/jit` to your PostCSS configuration _(instead of `tailwindcss`) } ``` +> 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. + Configure the `purge` option in your `tailwind.config.js` file with all of your template paths: ```js @@ -118,7 +120,6 @@ There are a few items still on our todo list though that we are actively working - The `important` option does not yet support selectors (like `#app`). - 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. - 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. -- 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. 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. From 684e67fbbe05579e316e634419e2818f724b7861 Mon Sep 17 00:00:00 2001 From: Adam Wathan Date: Tue, 16 Mar 2021 11:16:53 -0400 Subject: [PATCH 3/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 767db93..fbac717 100644 --- a/README.md +++ b/README.md @@ -42,7 +42,7 @@ Add `@tailwindcss/jit` to your PostCSS configuration _(instead of `tailwindcss`) } ``` -> 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. +> 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. Configure the `purge` option in your `tailwind.config.js` file with all of your template paths: