[JIT] Add support for "raw" purge content

[bradlc]

Fixes #4094

This PR adds support for specifying raw content as part of the purge config, mimicking the PurgeCSS API:

module.exports = {
  purge: [
    './src/**/*.html',
    { raw: '<div class="bg-red-500"></div>' },
  ],
}

You can also specify an extension which is used to select the appropriate extractor:

module.exports = {
  purge: {
    content: [
      {
        raw: '<div class="bg-red-500"></div>',
        extension: 'html',
      },
    ],
    options: {
      extractors: [
        {
          extractor: (content) => { /* ... */ },
          extensions: ['html'],
        },
      ],
    },
  },
}

[codecov-commenter]

Codecov Report

Merging #4272 (a0b2de7) into master (76c670f) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #4272      +/-   ##
==========================================
+ Coverage   71.10%   71.15%   +0.04%     
==========================================
  Files         218      218              
  Lines        4703     4711       +8     
  Branches      770      773       +3     
==========================================
+ Hits         3344     3352       +8     
  Misses       1273     1273              
  Partials       86       86              

Impacted Files	Coverage Δ
src/jit/lib/expandTailwindAtRules.js	80.88% <100.00%> (+0.57%)	⬆️
src/jit/lib/setupContext.js	72.79% <100.00%> (+0.27%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 76c670f...a0b2de7. Read the comment docs.

[adamwathan]

🤘🏻

[chasegiunta]

@bradlc Would you mind double-checking if the custom extractor (or defaultExtractor) is working correctly / running on watch changes?

I've pulled master (canary) and working with this functionality today, and I'm able to get options.extractors.extractor to work great on initial run, but upon changing the file in watch mode, the extractor is not being used.

[chasegiunta]

Apologies, ignore me, I guess it's a known restriction that custom extractors won't with JIT.

[caseywebdev]

@adamwathan this seems to have been reverted in the latest release, any reason why? Was hoping to use it.

[adamwathan]

Not reverted just not released yet. You can use our canary build to try it right away if you like!

npm install -D tailwindcss@canary

[caseywebdev]

Ah, my bad, I had assumed it would be in today’s release.