Skip to content

Instantly share code, notes, and snippets.

@bjo3rnf
Created August 14, 2019 16:31
Show Gist options
  • Save bjo3rnf/ef8afce3dc0844e92758a9b1fb5a4412 to your computer and use it in GitHub Desktop.
Save bjo3rnf/ef8afce3dc0844e92758a9b1fb5a4412 to your computer and use it in GitHub Desktop.
Tailwind CSS in a Symfony Project with Webpack Encore and Purge CSS
const Encore = require('@symfony/webpack-encore');
const tailwindcss = require('tailwindcss');
const autoprefixer = require('autoprefixer');
const purgecss = require('@fullhuman/postcss-purgecss')({
content: [
'./templates/**/*.twig',
'./assets/js/**/*.vue',
'./assets/js/**/*.js',
],
defaultExtractor: content => content.match(/[\w-/:]+(?<!:)/g) || [],
});
Encore
.setOutputPath('public/build/')
.setPublicPath('/build')
.addEntry('js/app.js', './assets/js/app.js')
.addStyleEntry('css/app.css', './assets/css/app.scss')
.enableSingleRuntimeChunk()
.cleanupOutputBeforeBuild()
.enableSourceMaps(!Encore.isProduction())
.enableVersioning(Encore.isProduction())
.configureBabel(() => {
}, {
useBuiltIns: 'usage',
corejs: 3
})
.enableSassLoader(sassOptions => {
}, {
resolveUrlLoader: false
})
.enablePostCssLoader(options => {
options.plugins = [
tailwindcss,
autoprefixer,
];
if (Encore.isProduction()) {
options.plugins.push(purgecss);
}
})
.enableVueLoader()
;
module.exports = Encore.getWebpackConfig();
@shmshd
Copy link

shmshd commented Sep 29, 2019

So, what if we need page-specific purging of CSS? that way each page contains its own CSS.

@bjo3rnf
Copy link
Author

bjo3rnf commented Sep 30, 2019

Hm, I don't think this is required if you go all Tailwind as the resulting CSS will be really tiny due to the concept of utility classes. Plus I don't know how this should be done. Purge CSS can only scan the markup of your template files and has no knowledge of 'pages'. You can add dedicated entry points for those pages but as stated in the beginning that wouldn't make any sense to me.

@sponno
Copy link

sponno commented Apr 27, 2020

Epic. Thanks that sorted my build.

@shmshd
Copy link

shmshd commented Apr 29, 2020

Purging won't work properly if we are using Symfony Form

@sponno
Copy link

sponno commented Apr 30, 2020

@shmshd I use the tailwind_layout HTML template. When Symfony generates forms, it uses a bootstap layout. I would recommend you customise your form building to use the Tailwind layout (you will need to google this to figure out how to change it). Then purgecss will find this document and will know to keep these classes.
hopefully that makes sense.

@jonathanacadomia
Copy link

Purging won't work properly if we are using Symfony Form

Hi, i had the same problems, i finally use the whitelist option in purgecss (wrap your css between /* purgecss start ignore / and / purgecss end ignore */ ). I hope it can help :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment