"When will it be compatible with Tailwind 4?"

[Skgrendel]

"When will it be compatible with Tailwind 4? I'm looking forward to using it, and I'd like to know if there's an estimated release or any updates on this compatibility."

[lrljoe]

There's only a handful of breaking changes with Tailwind 4, so it won't be too bad to add in at a glance, the main issue being avoiding duplication/clashing, or breaking things entirely (e.g. needing to support both import approaches)

There's a handful of bug fixes, and some minor changes to do, along with some further rationalisation/standardisation, which will make it smoother to add in.

I'm hoping to look in the next week or so at precisely how much work it is going to be, at which point I'll be able to give a guestimate at a release date.

The nice shiny utility elements of tw4 however are likely to come down the line a bit further.

Given that we will have to add in an isTailwind4 etc, it will add in some performance overhead, which is something that I'll need to think about, especially for a td cell for example.

[lrljoe]

Before I embark on adding in all of TW4, it'd be good to understand the level of demand for it, if anyone is eagerly awaiting this, please do give a thumbs up or similar on this.

[lrljoe]

Given there's 9 upvotes, and 2.1m installs in total, while I fully plan to add it in, the first logical step to my mind will be adding in a toggle for TW4 which will default to TW3 classes at present, which will allow other contributors to fix the class order etc.

There's a pretty sizeable update coming for the package, so I need to figure if I can include this or not.

[Baertie]

@lrljoe any update?

[lrljoe]

I'm presently updating tests and docs for v4.0, which while it isn't fully compatible with Tailwind v4, all of the logic to enable compatibility is added in.
i.e. all views that have a Tailwind 3 class set, have a placeholder for Tailwind 4 (currently set to Tailwind 3 classes).

Once all of the above is complete (should be by the end of the month), then it will be a relatively simple matter to replace deprecated Tailwind 3 classes in the Tailwind 4 placeholders.

V4.0 brings a lot of improved behaviour/performance, and several new features, which is why it's taken a while to get to this stage.

Fortunately as I'm at the tests/docs stage, it shouldn't be too far off now.