@source inline can't select all

[stephenasuncionDEV]

What version of Tailwind CSS are you using?

For example: v4.0.14

What build tool (or framework if it abstracts the build tool) are you using?

For example: Next.js 15.3.5

What version of Node.js are you using?

For example: v20.9.0

What browser are you using?

For example: Brave

What operating system are you using?

For example: Windows

Describe your issue

Tailwind v3 allows this safelisting with the following pattern, /./. We should be able to do the same in v4 with @source inline

Just did a quick glance, doesn't seem to be possible for now. Looks like the parsers look for specific keywords when compiling "candidates"

[wongjn]

Thank you for the suggestion. I've converted your issue to an Ideas discussion post as that's where we put feature requests 👍

[rozsazoltan]

I think it never seems like a good idea to include every class in production. But what does "every even mean? There are virtually infinite possible combinations to begin with. I believe that when you're building something dynamic, it's always a better idea to look for a CSS-based alternative that relies on proper use of CSS variables. Of course, this is just a personal opinion, but I like to share it for those who may not fully realize the downside of unnecessarily large file sizes caused by an overused safelist.

Related from here: https://discord.com/channels/486935104384532500/1389337876667306154/1389338994633998468

[stephenasuncionDEV]

I agree it's not ideal, but in my use case, I'm trying to render dynamic React code using libraries like react-live or react-runner. The code I'm running is generated by an LLM, so using Tailwind is ideal. I believe Anthropic's artifacts are still using v3, just so they can safe list all, ref: https://www.claudeusercontent.com/_next/static/css/c580c99cb3d2a9e1.css. Is there a better way to do this?