Neovim is broken with tailwindcss

[ghost]

What version of Tailwind CSS IntelliSense are you using?

v0.7.0

What version of Tailwind CSS are you using?
What version of Tailwind CSS IntelliSense are you using?

v0.7.0

What version of Tailwind CSS are you using?
v2.0.4

What package manager are you using?

npm

What operating system are you using?

Debian 11

Reproduction URL

neovim/neovim#19118

Describe your issue

Neovim is very popular editor but tailwindcss not working properly with it. All other LSP working fine. Probably some problems in tailwindcss implementaion. When i use completion menu - memory growing and growing slowly beyound 1GB, some documentation, cache - don't know. Any idea what's going on?

175874963-2d2c1992-779e-4709-9d68-02bbd74ba075.mp4

[toto1384]

Same problem here

[tomchart]

ditto

[jones-sam]

I have the same issue. I had it working before with coc, but now with nvim lsp tailwind is taking a bunch of ram and making neovim run laggy

[luiscassih]

Having the same issue, tried a few older versions and only 0.0.5 seems a bit faster and less memory usage, but still, using 300mb+ is not a good experience :/

[siblanco]

Yup can also confirm. Memory usage goes to the moon and neovim gets laggy.
Happens only when the tailwind lsp is attached and actually suggesting classes...just being attached does not affect the memory usage.

[hamooo-d]

did you guys find any solution? even if it's a temporary, tailwind LSP is starting to get annoying to work with.

[siblanco]

@hamooo-d unfortunately no, nothing new. Here are more details: neovim/neovim#19118 (comment)

To me it looks like an issue with nvim-cmp. I have no problems when using the lsp without nvim-cmp.

[Shougo]

It seems nvim-cmp problem instead of nvim-lsp.

[ghost]

Some explonations:
hrsh7th/nvim-cmp#1009 (comment)

[ghost]

hrsh7th/nvim-cmp#1009 (comment)

@hrsh7th @bradlc any idea why tailwindcss server always returns the 9k items?

[bradlc]

It returns ~9,000 items because that's how many Tailwind classes are available. We actually just did a lot of work to reduce the total size of the completion response and it's about 90% smaller than it was (assuming your client supports itemDefaults), so hopefully you will see a difference 👍

[folke]

This has been fixed in nvim-cmp in the meantime

[ghost]

This has been fixed in nvim-cmp in the meantime

any plans for async implementation in the future?)

[folke]

My PR also improved performance and tbh it's good enough for me for now :)