Passing additional content paths to tailwindcss

I can see the need and the use case, but one issue boggles me. AFAIK the CLI only supports shell wildcards, but not the JS globbing patterns. So things like

module.exports = {
  content: [
    './pages/**/*.{html,js}',
    './components/**/*.{html,js}',
  ],
}

will not work in a YAML/CLI config. I'm not using component libs, but I fear one would have to list dozen of component directories here one by one.

I gave this some more thought and it realized that it doesn't make much sense to rescan the same static assets on every single (uncached) request...

Closing as per #3

Just for reference:

Classes/styles dynamically generated on client side are not (and can not) be detected by this module, because by design this module only inject styles rendered on server side. Workaround for fully client side generated styles are either Tailwind's safelist config option

/* tailwind.config.js */
module.exports = {
  ...,
  safelist: [
    'bg-red-500',
    'text-3xl',
    'lg:text-4xl',
  ],
  ...,
}

or you can create kind of "dynamic safelist" by including a hidden div in your template, e.g.

{# node_with_external_js_library.html.twig #}
<div {{ atributes }}>
  <div id="placehoder_rendered_on_clientside_by_js_lib"></div>
</div>
{{ attach_library('my_module/clientside_js_rendering') }}
<div class="!hidden bg-red-500 text-3xl lg:text-4xl">this works like a dynamic safelist</div>

I'm re-opening that ticket because the same idea can be used to include CKeditor text styles into the safelist. Instead of manually adding classes into Tailwind's safelist, the module could automatically scan ~/config/sync/editor.editor.*.yml for styles used in WYSIGWYG editor formats.

After playing around with in our own projects, I'm going to close this again. Combining this module with a list of content/template files is counter-productive and just leads to very slow compile times and bloated CSS.

TailwindCSS' content list is meant to be used as a reducer/purger for CSS, not to add additional rules. To add additional classes/rules to your CSS, use Tailwind's safelist feature instead.