Back

@oliverandrich Maybe force a 3-major release or skip to 4 to target/match Tailwind CSS 4?

I'm looking forward to using it.

@webology Yes, I think I will jump straight to 4.x. I think it is a good decision to align the dependent library with the upstream version.

@oliverandrich I'm excited by 4, but I wonder if people will stay on 3 for the foreseeable future?

Not sure if your <4 version is going to stick around for a while.

@webology Yeah, I can imagine this. I am already thinking about keeping a branch with the 3.x code around. Or I make it a setting. Lot of things to think about at the moment. I had a discussion with a developer from my company today, and now I see a necessity to support both versions.