Quick demo of JS config file support and plugin support in the latest Tailwind CSS v4 alpha 🫣

One thing I didn't mention in the video — because plugins can be registered in CSS in v4, you can tuck the registration behind a CSS file that you just import. I expect most plugins in v4 to ship CSS files with an `@​plugin` hidden inside, so your CSS will look super vanilla:

Whoaaa, the block body on the @ plugin is pretty cool!

Just to confirm, does alpha mean: "wow that guy is such an alpha for running this on prod"? Or is there some other meaning to it?

How can we disable the default colors in the v4 config?

Explained here:

This is so cool! Question - with prefixing, will there be a way to use external CSS variables inside the `theme` directive, if they follow the naming conventions? Say I have a bunch of tokens already defined like `--acme-color-potato` - can I "import" them somehow?

Not at the moment but maybe something we could figure out. What would you want the external file to look like exactly, just a :root with some variables inside? Would need to be pretty simple for us to map it to a theme.

Love it Adam! Looking forward to more!

module.exports 🙈

Will always be better 🙃 But ESM works too 👍