v2.0.0

Supports Tailwind v1.0 (follow the migration guide).

Upgrade the plugin's default configuration, then apply your customizations to it:

vue invoke @ky-is/tailwind

v2.0.0-beta.2

• Support builds with empty style files (fix #7)
• Update dependencies to supported Tailwind betas >= 6
• Add inset to theme extensions

v2.0.0-beta.1

• Support TailwindCSS v1.0.0-beta
• Default postcss-preset-env to stage 0 (allows everything to work out of the box, and there's no drawbacks if you aren't using those features)
• Update the readme with more information on custom configurations and caveats

Note that Tailwind v1.0.0-beta.5 has a bug that makes it incompatible with this plugin, so the dependency is pinned to beta.4. This issue is fixed for the next Tailwind beta (see tailwindlabs/tailwindcss#858).

v1.7.0

• Improve PurgeCSS classname regex to fix caveat with Vue's object class binding syntax
• Simplify PostCSS config

v1.6.0

• Only enable purgeCSS in production builds (#4)

v1.5.0

• Update to Tailwind v0.7
• Whitelist Vue's generated classnames by default (for <router-link>, <transition>, <transition-group>)
• Expanded default config classes

1.4.0

• Improved PurgeCSS detection for duplicate CSS classes when using @apply

1.3.0

• Removes dependency on postcss-import (using ~ syntax to reference node_modules in css @import)
• Includes group-hovervariants for visibility by default
• Adds .pcss file support

Upgrading notes: You can delete the "postcss-import" entry from your package.json "devDependencies".

1.2.0

• Generate assets/styles/tailwind as .postcss file for better linting/syntax highlighting.

1.1.1

• Support special characters in class names (i.e. .w-1/2)
• Import tailwind.css via css import for new projects