tailwindcss-intellisense VS twin.macro

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.

Twin Macro Github Repo. This is a great resource to help you pick up Twin’s syntax, learn more about the package, and keep up to date with the latest releases.

Personally I like twin.macro the most. It’s similar to the above but based on Tailwind.

twin.macro is a library that allows you to use these styles in your JavaScript code. This library works exactly like styled-components.

One of the more promising alternatives is twin.macro - a Babel macro that processes Tailwind classes to generate JS objects understandable by various CSS-in-JS libraries. The developer experience (DX) of using it is amazing as you not only get all of Tailwind’s features without much change to your code, but you also get much more flexibility - all that on top of the traditional benefits of CSS-in-JS. Here’s an example code:

twin.macro

If you use Tailwind with React a lot, and are wanting support for Styled Components, give Twin Macro a look. They're close to finishing support for TW v3 in their Releases section :)

The blocker for us using it is our use of an excellent library called twin.macro which is built against babel's transpilation APIs to parse tailwindcss directives at compile time so that they may be used with css-in-js libraries. This efficiently bundles your css so that you only ship the precise css you use. The problem is, it's all quite slow.