Closed rchl closed 2 years ago
I'm not sure why this check for node_modules already existing was there.
I have a theory. Once upon a time, there was this code: https://github.com/sublimelsp/LSP-html/blob/73b085581f2094173f45e99bc668889488ec600e/plugin.py#L17
I guess we just migrated that piece of code to lsp_utils from the past code when we were starting with LSP-* plugins.
Now that check is not necessary, because there are other ways to determine when to update the server.
Thanks for digging. :) Let's try it.
This fixes an issue that would only potentially affect developers working on LSP-* packages.
If someone did an
npm install
in, for example, a localLSP-pyright/language-server/
repository then lsp_utils would not runnpm install
even after dependency is bumped inpackage.json
which means that ST would use old version of the server.I'm not sure why this check for
node_modules
already existing was there. Sinceinstall_or_update
only runs whenneeds_installation
decided that it needs to be installed, it seems to make sense to do it unconditionally. But I might be forgetting some case that it optimized...@predragnikolic this is likely the reason you had similar issue before with server not updating.