Closed Gaspartcho closed 3 months ago
It looks like this won't work if the user doesn't have node installed on their system, right? If that's the case we can't merge this, as the plugins in this repo are supposed to automatically make the servers work.
You'd need to also create a node
library
as a dependency of lsp_python
, in a similar way that's being done in #12.
Yes, I haven't noticed, I'll get right to it.
Also I noticed that NodeJs provides more binaries than the four already specified ones ("x86_64-linux", "x86_64-windows", "x86_64-darwin", "aarch64-darwin"). Should I add the remaining?
Also I noticed that NodeJs provides more binaries than the four already specified ones ("x86_64-linux", "x86_64-windows", "x86_64-darwin", "aarch64-darwin"). Should I add the remaining?
Sure, feel free to.
The nodejs
dependency should have the optional
property set to true, to allow people who already have it installed to choose not to install it.
Did you test it?
Just did. Seems to work fine.
EDIT: Except for installing, because lpm still crashes each time I try to install the nodejs
library
EDIT 2: Also I have forgotten to update the installed path for the library in the lua script, should be updated now
I just realized that the file extension for the Pyright archive was in .tgz
, which would prevent it from being automatically extracted by lpm
on install. However, from what I understood, the only difference with a .tar.gz
file would be the file name itself.
What should I do? Try to add .tgz
support to lpm
(by modifying one line), or change mirror for Pyright?
note: I initially choose to take the package provided by npm
because it was lighter than the GitHub version and did not contained the Vs Code extension.
The lighter the better.
Things to do:
This last change was not correct.
What issues did you get with language_python
as a dependency?
I was running some tests, and I tried to uninstall lsp_python
, and lpm tried to uninstall language_python
, as it became an orphan dependency, but failed, as it is a core addon.
Maybe there was a better solution though...
If that's the case, this is an LPM bug. Feel free to report it, or I'll do it later.
Turns out that what was preventing the nodejs
library to be installed was that the archive containing the binaries used the GNU TAR format, which was different from the one supported by microtar
(v7). I've submitted a PR which should fix this (I tested it and it looks like it was working).
Is it ready to be submitted for merge?
Is there anything else I need to add or is this PR ready to be merged?
I think the only decision at this point is about the optionality of nodejs
, @adamharrison.
Tested this, looks good to me!
The version of Pyright used here is the version packaged by Node-Js (hence the download link in
manifest.json
heading to their domain).I am not sure about the checksum value, as this is the first time I am working with this. (I generated it form https://emn178.github.io/online-tools/sha256_checksum.html)
This PR should resolve #8 , even though it is not using the same server to do it.