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
The issue is that the upgrade guide seems incomplete without a mention of this as a breaking change, or guidance on how to upgrade for those of us who rely on the functionality provided by safelist
Use the @config directive to load a legacy JavaScript-based configuration file:
@config"../../tailwind.config.js";
The corePlugins, safelist and separator options from the JavaScript-based config are not supported in v4.0.
Nevertheless, you're right. By the way, an alternative should be written in the Docs. The safelist was commonly used in packages, which were then used by a further third party.
The
safelist
property seems to have been removed from the tailwind config objectI cannot find any mention of this in the upgrade guide:
https://tailwindcss.com/docs/upgrade-guide#changes-from-v3
This v4 alpha announcement implies that this was going to be supported before a stable release:
https://tailwindcss.com/blog/tailwindcss-v4-alpha
The issue is that the upgrade guide seems incomplete without a mention of this as a breaking change, or guidance on how to upgrade for those of us who rely on the functionality provided by
safelist
These discussion questions indicate similar confusion:
tailwindlabs/tailwindcss#14462
tailwindlabs/tailwindcss#15291
The text was updated successfully, but these errors were encountered: