Using Tailwind CSS 1.4’s built-in PurgeCSS Options with Sage 9

sage
,
4

@kpoxo6op Since you are using Tailwind CSS 1.4, I’d recommend using the new built-in PurgeCSS feature. You configure it like so:

// tailwind.config.js
module.exports = {
  purge: {
    content: [
      // relative path globs to template files
    ],
    options: {
      // purgecss options (e.g. whitelist: [], etc.)
    },
  },
  theme: {},
  // etc.
};

The built-in PurgeCSS feature only purges when the NODE_ENV is production as well, it has a preconfigured default extractor (this is what I suspect is causing you issues above, since that guide was not Tailwind specific, but I had included the default extractor in the old Tailwind guide).