Try DropCSS

[leeoniya]

Instead of spamming other libs' issues inviting people to try DropCSS, I'll just cc them here.

Try DropCSS live: https://codepen.io/leeoniya/pen/LvbRyq

[leeoniya]

cc @mdickopp (via FullHuman/purgecss#195)

[zavr-1]

@leeoniya bro this is superb library!!! thanks so much.

[leeoniya]

@zavr-1 glad you like it :P

[leeoniya]

cc @zachleat, @andybelldesign could be a good fit for eleventy & hylia

[leeoniya]

cc @mlescaudron via purifycss/purifycss#202

[leeoniya]

cc @lmrwork

[leeoniya]

cc @advanced-site-checker (via FullHuman/purgecss#211)

[leeoniya]

cc @lucasvazq (via FullHuman/purgecss#212)

[lucasvazq]

The youtuber spammer boy but now in github kjj

[leeoniya]

cc @XhmikosR, @luwes (via FullHuman/purgecss#356)

if you can manage to get everything into an html string, DropCSS will probably work well for you(s)

[luwes]

@leeoniya using this config

    purgecss({
      content: ['./public/**/*.{html,js}'],
      defaultExtractor: content => content.match(/[\w-/:]+(?<!:)/g) || []
    }),

can DropCSS handle that?

[leeoniya]

there's a generic shouldDrop callback, so yeah, you'd just have to glob/walk the files and build up the whitelist to test against however you need. however, you'd be missing out on a lot of dropcss's benefits by just pulling all strings out of the html files; it really shines when you let it parse the html files so it can actually properly test the selectors against the dom structure and not rely entirely on overly-zealous whitelists, which is how purgecss works (the more you add the less effective it is at purging).

[luwes]

thanks, I might optimize on this later.