Skip to content
This repository was archived by the owner on Oct 16, 2020. It is now read-only.

Commit c2b9677

Browse files
committed
📝
1 parent f2f1a10 commit c2b9677

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

README.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55

66
## Install
77

8-
### Tailwind 1.0
8+
### TailwindCSS v1.0
99

1010
```console
1111
vue add @ky-is/tailwind@next
@@ -16,7 +16,7 @@ When the plugin is updated, you can upgrade your configuration with:
1616
vue invoke @ky-is/tailwind
1717
```
1818

19-
### Tailwind 0.x
19+
### TailwindCSS v0.x
2020

2121
See the [`tailwind-0.x` branch](https://github.com/ky-is/vue-cli-plugin-tailwind/tree/tailwind-0.x).
2222

@@ -49,11 +49,7 @@ Any CSS class that isn't used inside your `.html` files in `public/`, or by your
4949

5050
### 3rd-party CSS
5151

52-
If you're importing CSS from a 3rd-party library, you'll need to add its source files to PurgeCSS's search paths in `postcss.config.js` via the `content` array so it knows they're in use, or `whitelist` the imported classnames so they're never purged.
53-
54-
As an example, `vue-good-table` requires importing its bundled CSS classes. Since PurgeCSS doesn't see those classes being used anywhere, by default they'll be removed from your production build.
55-
56-
There's two approaches to fix this:
52+
If you're importing CSS from a 3rd-party library, you'll need to add its source files to PurgeCSS's search paths in `postcss.config.js` via the `content` array so it knows they're in use, or `whitelist` the imported classnames so they're never purged. As an example, `vue-good-table` requires importing its bundled CSS classes. There's two approaches to ensure its classes aren't purged from your production builds:
5753
- Add `'./node_modules/vue-good-table/src/**/*.vue'` to the `content` array (so PurgeCSS sees these classes being used)
5854

5955
Or:

0 commit comments

Comments
 (0)