Discover the latest updates.
Full Changelog: https://github.com/nuxt-community/tailwindcss-module/compare/v5.1.1...v5.1.2
Full Changelog: https://github.com/nuxt-community/tailwindcss-module/compare/v5.1.0...v5.1.1
cssPath
with resolvePath
by @dcrall in #465Full Changelog: https://github.com/nuxt-community/tailwindcss-module/compare/v5.0.4...v5.1.0
Full Changelog: https://github.com/nuxt-community/tailwindcss-module/compare/v5.0.3...v5.0.4
Full Changelog: https://github.com/nuxt-community/tailwindcss-module/compare/v5.0.2...v5.0.3
Stable version is out and ready for feedback ๐
Please read carefully the v5.0.0-0 release notes.
Tailwind CSS
by @hmaesta in #417tailwindcss/resolveConfig
with extension by @Ricklin90085 in #426Full Changelog: https://github.com/nuxt-community/tailwindcss-module/compare/v4.2.1...v5.0.0
You can try v5 by installing @nuxtjs/tailwindcss@5.0.0-4
with the package manager of your choice.
๐ Some bugs are expected with this release. Please open an issue if had trouble with v5 upgrade.
jit
option if was already using~tailwind.config
import renamed to #tailwind-config
when importing the generated Tailwind config in the applicationtailwindcss:config
hook is being called when modules are being installed for more predictable building behavior. Any module extending tailwind config should be installed before tailwindcss module89382fc
](https://github.com/nuxt-community/tailwindcss-@tailwindcss/jit
dependency (#340)Switch from postcss-nested to postcss-nesting to respect CSS Nesting spec we supported with version 3 of the module.
PostCSS 8 is now possible thanks to @nuxt/postcss8! No more compatibility build to use the latest version of Tailwind now โจ
Make sure to read the installation steps.
You may have heard about the Just-In-Time compilation mode of TailwindCSS, this version supports it, simply set the jit
option in your nuxt.config.js
:
export default { buildModules: ['@nuxtjs/tailwindcss'], tailwindcss: { jit: true }}
With jit
option, our build on nuxtjs.org came from 40s to 7s โก
tailwind.config.js
(#286) (62526cf) (resolves nuxt/nuxt.js#8971)build.postcss.plugins
as Array
is not supported anymoreWe now have a documentation website: https://tailwindcss.nuxtjs.org
@nuxtjs/tailwindcss
now configures the purge option of TailwindCSS and let the user extend it easily to keep a minimal tailwind.config.js
templatetailwind.config.js
will actually do a full Nuxt server restart but will actually fix the plugins update issueUpgrade Tailwindcss to v1.6.0
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.
nuxt build
(977d605
)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.jsmodule.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.3.4
โจexposeConfig
option to reference resolved config in javascript runtime (PR #69)See demo and source code
v1.1.4
purgeCSSInDev
option to activate purgeCSS in development mode1.1.3
build.postcss.plugins
syntax (#36)See changelog
See changelog
See changelog