[v4] Using build time environment variables in tailwind

[jason-johnson]

I want to create my project once and apply it to multiple, diverse environments. The environments are differentiated based on environment variables. For example, I will probably have a "primary"/"secondary" colour scheme which applies to all projects but the actual colours depend on the client they are for.

In previous versions of tailwindcss, one could use environment variables in the tailwindcss.config file but the new direction seems to be to move away from this file so it's not clear to me how to handle this use case now. I saw that CSS has an env() function but this seems to be something for run time and what I need is at compile time.

How is the best way to handle this use case now?

[ValerioDContinuum]

I need to handle exactly the same case.
TW v3 with js config files was really simple & clean to manage.
Any clue for a clean way of doing this in v4?

[benblustey]

Any luck with finding a solution? Seems like it was a set backward by removing the feature of reading .env files for easy configuration.

[antoniormrzz]

This is the main reason we still have our js config. We have safelist and specific files that are included in dev but not in production. I don't understand how thousands of people haven't commented on this? Does everyone just include all of their storybook files in prod?? @wongjn Please take a look.