Skip to content
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

Fixed animation on Welcome page and used Tailwind 3 compatible classes #91

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Bosphoramus
Copy link

Hey! I fixed the animation on the Welcome page and updated everything to work with Tailwind CSS v3, right now its the version the Vue starter kit uses, because shadcn/vue does not support Tailwind 4 yet. I built a custom variant so that when you use something like starting:opacity-0, it now generates CSS that nests the rule inside an @starting-style block—just like the native at-rule is meant to work. This is why the initial animation was broken.

Please take a look and let me know what you think.

@tnylea
Copy link
Contributor

tnylea commented Mar 31, 2025

Looks great @Bosphoramus. Hopefully, we can get Tailwind V4 out soon when ShadCN vue is compatible with v4, but for now, this makes the welcome page look identical 😊

Appreciate it!

@tnylea tnylea added the Approved Approved for merge label Mar 31, 2025
@Plytas
Copy link

Plytas commented Apr 1, 2025

@tnylea I just happened to check https://github.com/unovue/shadcn-vue repo and it seems like they are tagging a 2.0 release right now 😄

@Bosphoramus
Copy link
Author

Bosphoramus commented Apr 1, 2025

Ohh thats super nice @tnylea!

If you want i could do a PR to update to shadcn/vue 2.0 (the version that just came out) and Tailwind 4

I can also adjust the border radius CSS var, they are different between the React and Vue starter kits

@taylorotwell
Copy link
Member

Looks like we should just update this for TW4.

@taylorotwell taylorotwell marked this pull request as draft April 1, 2025 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved Approved for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants