Any plans to upgrade to React 19 and Tailwind CSS v4?

[harryworkbiz]

I was looking through the codebase and noticed that the prompts explicitly instruct the AI to use Tailwind v3, and the templates are using older versions of React and Tailwind rather than the latest stable releases (React 19 and Tailwind v4).

Is there a specific reason for this? Does upgrading likely cause issues?

[AshishKumar4]

Yes, so when I was developing this initially, in those days the best coding model we had was gemini 2.5 pro, and it's training data was a year or so behind (early 2024 or something), and thus it was super bad at working with the latest tailwind or react versions. So the specific versions used for packages in the templates are those that the model was most comfortable with at the time. The newer versions had some breaking changes and thus it was very easy for it to break the syntax and cause issues.

But haven't tested the latest LLMs on what versions have they been made familiar with, and thus haven't bothered to upgrade. Infact, even if they are comfortable with the latest ones, its likely that the amount of training material for the older versions would have been much more than the newer one simply because more time has passed for those versions.

But I guess if working with latest models, it should be possible, need a lot of testing though

[harryworkbiz]

That makes sense, especially given the limitations at the time. That said, most vibe-coding platforms today generate Tailwind v4 and React 19, and users will expect the latest versions by default. Agree it would need solid testing to avoid issues, but that’s good to know.

[charleshugie1988svg]

gh repo clone cloudflare/vibesdk

[charleshugie1988svg]

gh repo clone cloudflare/vibesdk