Is tailwindcss v4 (not beta) supported?

[baraknaveh]

What version of @tailwindcss/forms are you using?

0.5.10

What version of Node.js are you using?

v22

What browser are you using?

Chrome

What operating system are you using?

MacOS

Reproduction repository

n/a

Describe your issue

Not sure it's an issue, but is tailwindcss-forms supporting tailwindcss v4?

The https://github.com/tailwindlabs/tailwindcss-forms/blob/main/package.json don't seem to show that.

Thanks!

[tbremer]

came poking around for just this question, i've setup a new sveltekit project w/ tailwind 4 and forms do not seem to be working

@tailwindcss/forms: 0.5.10
node: v22.13.1
arc browser
macos

edit: sometimes you get to eat your own words very quickly. I found in the tailwind upgrade guide this bit about config support in Tailwind 4.

https://tailwindcss.com/docs/upgrade-guide#using-a-javascript-config-file

JavaScript config files are still supported for backward compatibility, but they are no longer detected automatically in v4.

If you still need to use a JavaScript config file, you can load it explicitly using the @config directive:

@config "../../tailwind.config.js";

it would be nice if the this repository's README file had something about the v4 change.

[RobinMalfait]

Hey!

Yeah Tailwind CSS v4 matches the >=3.0.0 semver range. The reason we had to add alpha and beta versions explicitly is because they are considered pre-releases and you don't want to accidentally install these when they are not proper releases yet.

[maxjacobson]

@tbremer

edit: sometimes you get to eat your own words very quickly. I found in the tailwind upgrade guide this bit about config support in Tailwind 4.

https://tailwindcss.com/docs/upgrade-guide#using-a-javascript-config-file

JavaScript config files are still supported for backward compatibility, but they are no longer detected automatically in v4.
If you still need to use a JavaScript config file, you can load it explicitly using the @config directive:
@config "../../tailwind.config.js";

it would be nice if the this repository's README file had something about the v4 change.

FWIW, I got this working post-upgrade in a slightly simpler way, by adding this line to my CSS file:

@plugin "@tailwindcss/forms";

Based on this that I found in the docs: https://tailwindcss.com/docs/functions-and-directives#plugin-directive

it would be nice if the this repository's README file had something about the v4 change.

For sure, agreed.

Even better would be if the auto-migrate script added that line for me automatically.

[baraknaveh]

Thanks @RobinMalfait for replying and pointing out! Looks like my bad, misdiagnosed the issue.

[strzibny]

Max's solution works however I am unsure how to switch the theme? Before I got the 'simple' styling, now I am getting the unstyled default. How to switch between the styles?