✨ improve(minor): reasonable defaults for purgecss (@roots/bud-purgecss)

[kellymears]

You don't have to call bud.purgecss in order to purge styles.

Shouldn't be a problem for anyone for any reason I can foresee but still a minor bump.

• Deprecates bud.purgecss method. Removal of this method constitutes a major bump imho, will save for v7.
• Provide reasonable defaults for purgecss
• Improve exports organization
• Improve typings (options API type hinting)
• Improve tests
• Improve examples/purgecss

Default behavior:

• purgecss is enabled in development mode only
• content is set to:
  • bud.path('@src/*.{html,js,jsx,php,pug,rb,ts,tsx,vue}')
  • bud.path('@src/**/*.{html,js,jsx,php,pug,rb,ts,tsx,vue}')

Updating config

This is pretty easy. The old setup involved calling

bud.purgecss({
  content: [bud.path('src/*.html')],
  css: [bud.path('src/**/*.css')],
})

This is now:

bud.purge
  .setContent([bud.path(`src/*.html`)])
  .setCss([bud.path(`src/**/*.css`)])

Or, as with all extensions, you can use the Options API directly:

bud.purge
  .set(`content`, [bud.path(`src/*.html`)])
  .set(`css`, [bud.path(`src/**/*.css`)])

I really like this style but the type hinting isn't as good.

If you really want to use the plugin in development mode for some reason, you can just call enable:

bud.purge
  .setContent([bud.path(`src/*.html`)])
  .setCss([bud.path(`src/**/*.css`)])
  .enable()

Type of change

PATCH: backwards compatible change