You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Tailwind v4, the tailwind.config.js is optional with configuration all done in CSS.
While I appreciate a future version of this tool will support v4, would it be possible to include a setting in the meantime that disables auto-generation of this file? Something along the lines of:
TAILWIND_CLI_DISABLE_AUTO_CONFIG_FILE=False
The text was updated successfully, but these errors were encountered:
I have something like that implemented and plan to release a package on the weekend, that supports Tailwind v3 and v4. I had to make up my mind, if I want to support both or switch all in to Tailwind v4.
I would think quite a few projects will still be using v3 for some time - it's not trivial moving over a large project, even with the upgrade tool. However I also understand supporting both versions might not be easy either.
In Tailwind v4, the
tailwind.config.js
is optional with configuration all done in CSS.While I appreciate a future version of this tool will support v4, would it be possible to include a setting in the meantime that disables auto-generation of this file? Something along the lines of:
The text was updated successfully, but these errors were encountered: