v2.1.0

Misc ✨

• Upgrade dependencies (TailwindCSS to v1.5.1).

If a new version of TailwindCSS goes out, you can always install it with npm install --save-dev tailwindcss, the module will use it directly.

Bug fixes 🐞

• Force production env for postcss on nuxt build (977d605)

v2.0.0

Version 2.0 is out, including TailwindCSS v1.4 ✨

This version is a breaking change since we actually removed nuxt-purgecss dependency, since Tailwind 1.4 has a purge option now!

If you are upgrading, take a look at the new tailwind.config.js:

// tailwind.config.js
module.exports = {
  /* ... your actual config */,
  purge: {
    // Learn more on https://tailwindcss.com/docs/controlling-file-size/#removing-unused-css
    enabled: process.env.NODE_ENV === 'production',
    content: [
      'components/**/*.vue',
      'layouts/**/*.vue',
      'pages/**/*.vue',
      'plugins/**/*.js',
      'nuxt.config.js'
    ]
  }
}

v1.4.1

• Upgrade dependencies and use Tailwind v1.3.4 ✨

v1.4.0

Features

• Add exposeConfig option to reference resolved config in javascript runtime (PR #69)

See demo and source code

Chore

• Upgrade dependencies

v1.3.3

• Fix: don't purge base and components (#65 by @hecktarzuli)
• Upgrade dependencies (#63)

v1.3.2

• Upgrade to Tailwind v1.2 (#60)
• Fix override PurgeCSS "enabled" option (#59)

v1.3.1

Fix a regression: PurgeCSS stopped working after upgrade to v.1.3.0

Related Issues: #52 and #54

v1.3.0

• Upgrade TailwindCSS to v1.1.4
• Add purgeCSSInDev option to activate purgeCSS in development mode

v1.2.0

• Upgrade TailwindCSS to 1.1.3
• Add support for deprecated build.postcss.plugins syntax (#36)

v1.1.2

• Upgrade to Tailwind v1.1.0
• Remove log of postcss preset (fix #20)
• Use nuxt.hook('build:before') to work when used as middleware (fix #23)