fix(tailwind): swap @tailwindcss/vite for @tailwindcss/postcss

[tylersayshi]

some nested components not working with the tailwind vite plugin. the hmr seemed broken when using the tailwind plugin as well.

related issue:
tailwindlabs/tailwindcss#16585

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
waku	⬜️ Ignored (Inspect)	Visit Preview	Feb 17, 2025 4:36am

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[dai-shi]

LGTM

[dai-shi]

@tylersayshi ah, we missed 07_cloudflare. please open a follow-up pr.

[rmarscher]

@tylersayshi Do you think Waku will switch back to the tailwind plugin instead of postcss since they are addressing the original issue? Does the tailwind vite plugin handle vendor prefixes based on browserslist? I couldn't find any mention of it.

[tylersayshi]

Do you think Waku will switch back to the tailwind plugin instead of postcss since they are addressing the original issue?

yes! tailwind released a change that is expected to fix the issues we were seeing, but we do need to still test those changes before recommending it again. If you have time to try out the tailwind vite plugin on your project(s) that would be helpful!

Does the tailwind vite plugin handle vendor prefixes based on browserslist?

no idea... sounds like a good question for the tailwind discussions board.

[dai-shi]

Please be aware we had two issues in the previous plugin. Another one was hot reload, right?

[tylersayshi]

Please be aware we had two issues in the previous plugin. Another one was hot reload, right?

right! i'd suspect we may need to do some work to integrate the plugin through the waku config viteConfigs field to get it working as expected all the time.