tailwindcss-intellisense VS unocss

It'll autocomplete classes in CSS with @apply, but it won't autocomplete custom classes from CSS in HTML

For fixing the tailwind's lsp we have to change some of the codebase of tailwind's lsp to make fix this issue for Neovim.

I don't have a full answer, but share your frustrations. This isn't easy to do until Tailwind support ES Modules [1] [2].

Seems others have had bad perf with tailwind lsp: https://github.com/tailwindlabs/tailwindcss-intellisense/issues/444

It should work now: https://github.com/tailwindlabs/tailwindcss-intellisense/pull/656 , you can see there was a problem: https://github.com/helix-editor/helix/issues/2213 but it was solved.

I don't know that. I actually don't have much experience with this kind but the language server code is available here.

I want to get LSP support when using tailwind-rn, but I cannot get the custom regex to work like described here.

You can install it by npm now https://github.com/tailwindlabs/tailwindcss-intellisense/tree/master/packages/tailwindcss-language-server and it's working.

I wish tailwind would support attributify like https://github.com/unocss/unocss, which is much more readable for complex layouts:

  link

I feel the same about people praising Tailwind.

Tailwind (and similar, I tend to use https://unocss.dev/) is not good for your frontend architecture BUT they allow you to be so fast, that it negates the benefits.

For a job well done, I'd follow the principles of https://maintainablecss.com/

I think UnoCss is may be better than Tailwind already and has a good Vue integration https://unocss.dev/

The most popular tools that implement this approach are: Tailwind, WindiCSS, UnoCSS.

- UnoCSS: https://unocss.dev/

haha, fair point. Still, I'm on the fence about how utility components are namespaced in USWDS. Perhaps giving users the flexibility to define the namespace might work better? One thing that bugs me is the absence of class-sorting like we have in TailwindCSS. Plus, there are some gaps I've noticed in USWDS. The naming, especially when comparing "padding-x-2" and "p-x-2", can be really annoying when switching around, maybe that could also be an option for the developer or project. Similar to the ideas antfu has on uno.css https://unocss.dev/ ♥

UnoCSS is a popular option

UnoCSS — for styling with Tailwind-like atomic CSS;

Some exceptional libraries and frameworks only support VSCode, which you could argue is a bad thing, but it makes sense, VSCode is the most popular code editor after all. For example UnoCSS only has a VSCode extension, and it's my favourite way to write CSS. Astro has a LSP but I've found that the experience in VSCode is much better than in Neovim.