Finally I switch to #vscode for developing front end work. It's super useful to see the converted class for #tailwindcss (I'm a beginner). I know there is lsp-tailwind, but I use eglot, and it cannot have multiple lsp server in one major mode yet.
But for Eglot AFAIK there is no way to achieve the same.
For your choice of tailwind, I was very enthusiastic about it in the beginning (out of frustration with sass and colleagues), but that quickly faded when the project grew bigger and I literally had 20+ tailwind classes in a single div tag.
@louis From the tailwind website I have learned that we can create our own css classes which can includes tailwind css? So 20 classes can be avoided I think? However, it may go against the purpose of using tailwind(use class directly without manually write down our owns). Though, I just use it for my small/middle group project, so I think it should be fine and the development time can be saved.
I'm quite stressful because of my decidophobia. I waste a lot of time back and forth the process of deciding to use #vscode for developing web front end.
@louis I used to hate #lsp-bridge. However, after trying it this time(the second time), but I find I quite like it now. The completion experience and inlay hint are really good.
@MeowKing I use Eglot now but I actually might switch back to lsp-mode, too. I have all kind of strange problems and often hit a limitation. Thanks for the inspiration!
Add comment