Awesome resource. Thank you 🙏🏼 More on reddit.com

Should be “@tailwindcss/forms” 👍🏻 don’t forget the “@“ sign! ... There was an error while loading. Please reload this page. Something went wrong. There was an error while loading. Please reload this page. ... My bad, I've missed the note saying it isn't available yet in v4 in the roadmap section. I hope this gets added soon! Plugins ... More on github.com

I'm happy to share with you guys tailwind-tools.nvim . A Neovim plugin inspired by the official vscode extension, using neovim built-in LSP client and treesitter to provide the same features (and more) as the vscode extension. The plugin currently provides: Class color hints and can be inlined like in vsocde but require nightly Class concealing using treesitter Class sorting without using prettier or external scripts An utility function for for displaying colors in the completion menu using nvim-cmp and lspkind. Other feature ideas and contributions are welcome! PS: I'm not that good at english and you can see it by the poor documentation so feel free to suggest some changes that could make it better. More on reddit.com

If you know what you are doing CSS-wise, I feel that the main benefit you get out of Tailwind is not having the overhead of separate CSS files (or having to write media queries yourself). If you don't know what you are doing, it makes it easier to write CSS that works exactly how you'd expect it to, on different devices and in different browsers. But as you say, it will really end up making your HTML unreadable if you have a fairly complex application. It sounds like some people in here think that this is a skill issue, but it is a very real problem that arises with Tailwind when you need to support light/dark mode and various :hover and :focus styles on many elements. They will have a ton of classes in these cases, there is no way around it. My take is: I use Tailwind on projects more and more, and you adapt to it. For example, I have started to search (in-file) for elements by class names that I know they have. Makes it a bit easier. I do really prefer how my components look using CSS modules, though - and I would use this every time in an ideal world - but I am lazy, and Tailwind is easy to set up with tree-shaking and everything. It is definitely not a perfect system, and the trade-off you point out is very real. More on reddit.com