We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The templates were migrated to Tailwind v4 in #70, but they still rely on tailwind.config.js|mjs|ts instead of adopting the new theming approach.
tailwind.config.js|mjs|ts
For example:
@theme { --color-*: initial; --color-inherit: inherit; --color-transparent: transparent; --color-current: currentColor; --color-black: rgb(0 0 0); --color-white: rgb(255 255 255); --color-lavender-blue-50: #f2f3ff; --color-lavender-blue-100: #e4e7ff; --color-lavender-blue-200: #c9cfff; --color-lavender-blue-300: #aeb8ff; --color-lavender-blue-400: #93a0ff; --color-lavender-blue-500: #7888ff; --color-lavender-blue-600: #606dcc; --color-lavender-blue-700: #485299; --color-lavender-blue-800: #303666; --color-lavender-blue-900: #181b33; }
Any help with migrating these configurations to the new method would be greatly appreciated.
Resources:
https://tailwindcss.com/blog/tailwindcss-v4
https://tailwindcss.com/docs/upgrade-guide
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The templates were migrated to Tailwind v4 in #70, but they still rely on
tailwind.config.js|mjs|ts
instead of adopting the new theming approach.For example:
Any help with migrating these configurations to the new method would be greatly appreciated.
Resources:
https://tailwindcss.com/blog/tailwindcss-v4
https://tailwindcss.com/docs/upgrade-guide
The text was updated successfully, but these errors were encountered: