Supporting yarn #167
Comments
Yes, this can be done. Example:
You just need to substitute |
Well this would have to be done in every lsp install script? |
AFAIK, the Maybe we could have the system check for |
what would be the benefit? |
I've been thinking about it for the past few hours, and it's kind of redundant to do this. Part being that |
Well... The benefit will be that there is a faster install on systems with Yarn. Also if the systems only have Yarn and not NPM, then the whole plugin fails. @derektata I am not sure about non-UNIX systems, but I know that it can be common to install only yarn on Linux based systems. I guess it eventually comes down to a users preference. But the whole plugin should not stop working because of that. I have been using |
npm is almost always installed when yarn is installed. I haven't noticed faster install times when installing a single package. |
@kabouzeid, I can understand where @ssbanerje is coming from when it comes to only having one installed. So I have an idea
|
@derektata That can be an annoying problem to fix! But it is really interesting that @kabouzeid Yeah. I think it is a yarn |
@ssbanerje I'll look into this more tomorrow, I just leveled up and enjoying a day off 🎂 |
@ssbanerje Good news, I found a fix for this, and I'll be submitting a pull request in a little while with the updated code. |
Is there any way to configure the install scripts to use
yarn
rather thannpm
?It seems like currently the install script using
npm
is hard-coded for almost every language server.The text was updated successfully, but these errors were encountered: