Closed predragnikolic closed 3 years ago
I noticed a bug where the LSP-typescript plugin won't start if the LSP-tailwindcss plugin don't start.
I can't quite see that happening.
Note that LSP-typescript also implements is_allowed_to_start
and won't start if there are no workspace folders.
I noticed a bug where the LSP-typescript plugin won't start if the LSP-tailwindcss plugin don't start.
I think it's a bug in LSP :) Before the early-exit in start_async
in plugin/core/windows.py, we should call this as well:
Thanks guys for the tips that you left in the previous PR.
Start the server only if the tailwind.config.js is present and if the user has tailwind css installed in node_modules.
How to test.
index.js
file.LSP-tailwindcss - no tailwind.config.js present in {PATH}
next
tailwind.config.js
file at the root.next in terminal type:
npm init -y
- that creates a package json file.npm install -D tailwindcss
NOTE:
I noticed a bug where the LSP-typescript plugin won't start if the LSP-tailwindcss plugin don't start.
index.js
file in an empty folder.