Upgrading Laravel Apps to Tailwind CSS 1.4

Published May 6th, 2020
2 minute read

Now that Tailwind CSS 1.4 is out it's a great time to upgrade your old, tired app. Okay, maybe your app already had version 1.3, but if not, the latest two versions (1.3 and 1.4) bring some amazing improvements. Most notable are the new space between utilities and built in PurgeCSS support.

Upgrading is easy! Run npm install (pro tip: npm i is a shortcut). You might need to double check your package.json file if that doesn't work for you. Make sure your version constraint allows updating to 1.4+ -- mine looks like this:

"tailwindcss": "^1.0",

So you've got the upgrade, but let's talk about how to use a snazzy new feature -- built in PurgeCSS support. If you're currently using the PurgeCSS Wrapper for Laravel Mix to add purgecss, we can remove it. Delete the laravel-mix-purgecss line from your package.json and run npm i once again.

Open up your tailwind.config.js file (you are using a config file, aren't you?)... add the new purge property. Your config file might look like this:

let defaultConfig = require('tailwindcss/defaultConfig')

module.exports = {
  // This is the new section
  purge: [
  	// Your options may vary
	"app/**/*.php",
    "resources/**/*.less",
    "resources/**/*.js",
    "resources/**/*.php",
  ],
  
  theme: {
    // ...
  },
}

You can pass any of the PurgeCSS options you were using with the laravel-mix-purgecss plugin to this too, it just requires a slightly different syntax:

purge: {
  content: [ 
    // an array of files to look for classes in
  ],
  options: {
	// options to be passed directly to PurgeCSS
  }
}

Take a look at your webpack.mix.js file. You should have a chunk like the following:

.purgeCss({
	// your config options here
})

Pass those same options to the new purge config in your Tailwind config file. Then you can remove them from your webpack config! Note that if you were using the default version of the laravel-mix-purgecss plugin you will need to be explicit about the files you want to search for classes to keep, as tailwind's new purge option doesn't look for any files or directories by default.

For more information, check out the Tailwind docs on Controlling File Size.

Make sure to test that your setup is working by running npm run prod. ✌️

Enjoy this article? Follow me on Twitter for more tips, articles and links.
😢 Awww, nobody has liked or mentioned this on Twitter yet.

Join the Newsletter ❤️

A most excellent monthly newsletter with code & design tips, curated links and more!
Don't worry, I'll never send you spam. Unsubscribe at any time.