Add ability to specify non-default language server and package.json path via LSP settings vol.2

[firu11]

Building on top of #77 by @GamerGirlandCo

You can now specify the relative path to "vue-language-server" via settings.json like so:

An example project/dir structure:

foo-project
├── backend/
│   └── ...
├── frontend/
│   ├── package.json
│   ├── node_modules/
│   └── ...
└── ...

settings.json:

{
  // ...
  "lsp": {
    "vue-language-server": {
      "settings": {
        "server_path": "frontend/node_modules/@vue/language-server/bin/vue-language-server.js",
        "package_json_path": "frontend"
      }
    }
  },
  // ...
}

It tries to find the lsp in this order:

1. from settings.json
2. from the hardcoded SERVER_PATH aka. the root dir
3. install from npm

I'm not a good rust programmer, please check the changes thoroughly. Thanks! 😅

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @firu11 on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

[firu11]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[hyperstown]

While manually specifying lsp working dir could be useful and that's how it was done back in the day eg in vetur:
vetur.config.js

module.exports = {
  projects: [
    {
      root: './src/frontend/', //root of subproject
      package: './package.json', // It is relative to root property.
    }
  ]
}

Currently most common approach would be to just use root markers.
LSP server scans recursively directories and looks for patterns like package.json, nuxt.config.js, vite.config.js, src/*vue.
That's how lspconfig works in nvim and how lsp servers work in vscode.
I guess that #91 shouldn't be closed unless we have proper root markers implementation.

[firu11]

I agree. This is just a temporary solution.

[firu11]

I've just tested the main branch and it seems to work without this workaround. I'm closing this for now.