feat: use stable tailwind flag

[MichaelDeBoey]

See remix-run/remix#5960

[runmoore]

Tested this change locally and it works perfectly 🥳

[machour]

@runmoore careful, you loose the autoprefixer that came free with tailwind

[runmoore]

@runmoore careful, you loose the autoprefixer that came free with tailwind

Sorry, I'm not sure what you mean. Could you elaborate? I thought this would be a no brainier, maybe I'm wrong?

[machour]

@runmoore juste a little inconvenience, that could be solved manually. Check this for more context: remix-run/remix#5475

[brophdawg11]

I think we should wait until future flags stabilize into a v2_ flag before we auto-enable them in templates/stacks. all the unstable_ CSS stuff should be getting rolled up into future.v2_dev in 1.16.0 so let's hold until then?

[mcansh]

you lose the autoprefixer that came free with tailwind

can we add a postcss.config.js file and autoprefixer as a devDep?

module.exports = {
  plugins: [require("autoprefixer")],
};

and add postcss: true to remix.config

[brophdawg11]

Just confirming, we have to wait until we release 1.16.0 before we can merge this, correct?

[MichaelDeBoey]

we have to wait until we release 1.16.0 before we can merge this, correct?

@brophdawg11 That's correct.
Hence why I keep this in draft for now

[silvenon]

Just wondering, why was tailwindcss added to the PostCSS configuration as well? Wasn't the fix only to add autoprefixer?