Persistence Flagging Tailwind Utilities

[Penderis]

Hi, my wording might be wrong in how I describe stuff, my apologies.
I don't think this is currently possible and if it is a link to the docs would be nice :)

Ok, so Tailwind basically scans all your code then matches that with css in your Tailwind CSS, it then compiles a CSS sheet with only what you have used. So if you have used red-900 then it will have red-900in the final CSS but it won't say have red-600

What if I wanted it to have the whole --color-red-* scheme?
More so I would likely want this also for something like the flex and grid utilities to easily then allow users to maybe build their own little rows and columns or choose "predefined" colors, even if they were my own --color-mycolor utilties.

A more clear example is how you would with the icky frameworks like bootstrap et al , opt-out I guess. With those you have to do the laborious work of including the grid, the menu, the thisthing and thatthing.

Tailwind removes all that hassle but I believe for "theming" like in Wordpress, Drupal etc it can be super useful to actually allow forcing big chunks of tailwind to still compile. One way I can describe it is , instead of me creating a kitchen-sink page using absolutely all classes I want to possibly have available - I can just flag entire sections like the grid-* utilties and have them compile to said file or same file.

[wongjn]

You will be able to do this with @source inline(). See #17147 for details. This feature is planned to be included in v4.1.

[Penderis]

Oh awesome. Thanx again.