-
Notifications
You must be signed in to change notification settings - Fork 355
Preline compatibilty with TailwindV4 #556
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
Comments
Just a heads-up, our team is actively working on ensuring compatibility, and the next Preline UI release will be fully compatible with Tailwind v4.0. Additionally, we haven’t encountered any plugin compatibility issues so far; the changes primarily involve updated classes between Tailwind v3.x and v4.0. We’ll include a comprehensive migration guide in our documentation to help you make the switch smoothly. Cheers! |
Thank you for your response. I am looking forward to the upcoming release. |
@jahaganiev Is there documentation on how to get this working with tailwind 4 yet? I don't see a guide anywhere on the website |
Hey @joetito1 - it's not out yet. We will include the detailed needed info to migrate Tailwind v4 once it's out. |
Any update? Sorry, I just got all the way through a migration to get here. My bad for not checking the first oc. I'm not trying to rush; just wondering about the status. Ty! |
Hey @red2678 - It's internally ready, and we're currently running final tests. We expect it to be released by the end of this month. |
please have an unstable branch of preline and maybe even an untested version because well yes. |
I was greatly frustrated after hearing the mighty benefits of Preline but couldn't get it to work. Today, it took me an entire 9hours figuring out how to implement Preline UI v2.7 with Tailwind v4, not knowing it's an error NOT from my novice experience 🥺🙄 |
I'm very disappointed that while all the other components have already been upgraded to Tailwind CSS v4, Preline still hasn’t provided support, so I’ve decided to replace all the Preline components |
Someone found a (temporary?) solution: #518 (comment) Plugin changes: BALOTIAS@b121e15#diff-b72c2a6d80daeb87d4852346d0f86bdb7c15f767737a0e1336a7070d9e31d271 I can confirm it works - tested with Astro 5.3 |
@jahaganiev are you still targeting today or do you expect further delays? |
I don’t see why everyone is in such a rush—Tailwind v4 was only released recently. Preline is an amazing headless library, and the team has already done a fantastic job. Let’s give them the time they need to refine things and introduce even more exciting features. Good things take time, and I’m sure they have some great updates in store for us! |
@PruthviPraj00 because people start new projects and it makes no sense to use Tailwind v3 right now. Any update on release date? |
Hey everyone, it should be out within a few days - apologise for the delay. Cheers! |
That's great, thank you I recently started experimenting with Tailwind, I'm coming from the vanilla model, HTML, CSS and JS |
You're retarded, right? You're probably a selfish individual from a primitive place where they still live in caves |
I am using laravel but my javascript is not working in laravel I have configured all the installed steps |
Hey everyone! Next, our team will focus on open Github Issues/PRs and updates for Framework Guides. Cheers! |
Great, thank you |
Hi @olegpix,
I wanted to discuss the recent Tailwind CSS V4 release and get your insights on the upcoming changes. I've been experimenting with Preline alongside Tailwind CSS V4, but I'm encountering an issue with the plugin configuration. Specifically, when trying to include the Preline plugin using
require('preline/plugin')
, I'm finding that the current plugin approach seems incompatible with the CSS file setup.Could you provide some guidance on the correct way to integrate Preline with the latest Tailwind CSS version?
Best regards
The text was updated successfully, but these errors were encountered: