-
-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
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
Tailwind v4 Support #1527
Comments
Saying no breaking changes is a bit misleading here I believe they mean no breaking style changes but the config changes are pretty massive. |
|
to clarify @ieedan , i meant no more breaking changes to be expected in tw tw Tailwind UI website has been fully migrated to |
for now, if you guys want to use tailwind v4 compatible with any new or existing app, it is pretty simple just run the codemod - npx @tailwindcss/upgrade@next so now the thing is you won't be able to add new components, as there won't be tailwind.config.js/ts anymore, so how do you add new components to your app? just create a temporary new project and run - npx shadcn@latest init -d
npx shadcn@latest add -a
npx @tailwindcss/upgrade@next and voila, you have a new tailwind v4 version of the components and css, just copy and paste required content if you wish to get this task automated, via CLI tool, feel free to emojify this comment and I will make one |
If anyone is interested, i converted the default shadcdn-svelte configuration.
By pasting this content into your app's css, you should be able to delete the tailwind.config.ts file without any differences |
missing @variant for theme toggling in config above I just whipped out a new CLI tool to experiment with @nextjs, @shadcn and @tailwindcss v4-beta you can try it too, at npmjs.com/package/shadcnext |
This is a tool for next not svelte |
ohh right, use steps than, should work |
Prerequisites
Describe the feature
Tailwind v4 just hit beta release an no breaking changes are expected. Would be cool to see a guide for shadcn-svelte on how to make the switch for some v3 users
(honestly not sure if it exists yet in shadcn but it will)
The text was updated successfully, but these errors were encountered: