Why is yarn required for the build?

[andradei]

Is your feature request related to a problem? Please describe.
If user has node but not yarn the project can't be built.

Describe the solution you'd like
Don't have a hard dependency on yarn especially when node is the standard.
Check if yarn is installed before depending on it, otherwise use node.

[andradei]

Also, as of today, the recommended way to install is by git cloning. If someone wants to integrate it with Mason so it can be installed via MasonInstall, they will have to check for the presence of yarn which is unnecessary.

[ndonfris]

I get your point, and have already been trying to rely less on the use of yarn for distributing this project (prior to this issue). However, there are plenty of lsp projects using yarn, and I assume some of them are included in mason. For example: awk-lsp, typescript-language-server, etc...

As a neovim user, I'm familiar with the project Mason. I would love to have this lsp be supported there. Although, I'm not exactly sure what you're proposing. By node are you referring to npm?

Would removing the preinstall script resolve your issue?

I package this project on npm, and in earlier versions it did not seem to always install correctly for some users. That is why the recommended installation method is to clone this repo. Feel free to contribute to any fixes towards the projects' installation process!

Note

I've tried porting the project to pnpm in favor of yarn but had difficulties getting everything working.

[dsully]

Having a GH release would help here as well in the mean time.