feat: migrate to vim.lsp.config #3659

Problem:
Nvim 0.11 has vim.lsp.config, which mostly replaces the legacy
nvim-lspconfig "framework".

Solution:
Migrate all configs to `lsp/*` variants. The old configs in
`lua/lspconfig/` are "frozen".

The new configs include these changes:
- `commands` field became raw calls to
  `vim.api.nvim_buf_create_user_command` inside `on_attach`.
- `root_dir` became:
  - `root_markers` whenever the file list was simple didn't need to mach `*`
  - if the logic was complicated, or needed to match something like
    '\*.c', it was defined as a vim.lsp.Config `root_dir` callback.
- `on_config_change` became `before_init`. I don't actually know if this
  is the correct approach, but looking around the documentation of
  `nvim-lspconfig` a saw that it was defined as the function that gets
  called as soon as the config have `root_dir`, and so I thought
  `before_init` might be the closest alternative.
- `docs.description` became a luadoc `@brief` docstring.
- `single_file_support = false`?

Co-authored-by: Aliou Diallo <aliou@users.noreply.github.com>
Co-authored-by: Justin M. Keyes <justinkz@gmail.com>

1 files changed, 81 insertions, 0 deletions

diff --git a/lsp/ts_ls.lua b/lsp/ts_ls.lua
new file mode 100644
index 00000000..dee204c4
--- /dev/null
+++ b/lsp/ts_ls.lua
@@ -0,0 +1,81 @@
+---@brief
+---
+---https://github.com/typescript-language-server/typescript-language-server
+--
+-- `ts_ls`, aka `typescript-language-server`, is a Language Server Protocol implementation for TypeScript wrapping `tsserver`. Note that `ts_ls` is not `tsserver`.
+--
+-- `typescript-language-server` depends on `typescript`. Both packages can be installed via `npm`:
+-- ```sh
+-- npm install -g typescript typescript-language-server
+-- ```
+--
+-- To configure typescript language server, add a
+-- [`tsconfig.json`](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html) or
+-- [`jsconfig.json`](https://code.visualstudio.com/docs/languages/jsconfig) to the root of your
+-- project.
+--
+-- Here's an example that disables type checking in JavaScript files.
+--
+-- ```json
+-- {
+--   "compilerOptions": {
+--     "module": "commonjs",
+--     "target": "es6",
+--     "checkJs": false
+--   },
+--   "exclude": [
+--     "node_modules"
+--   ]
+-- }
+-- ```
+--
+-- ### Vue support
+--
+-- As of 2.0.0, Volar no longer supports TypeScript itself. Instead, a plugin
+-- adds Vue support to this language server.
+--
+-- *IMPORTANT*: It is crucial to ensure that `@vue/typescript-plugin` and `volar `are of identical versions.
+--
+-- ```lua
+-- vim.lsp.config('ts_ls', {
+--   init_options = {
+--     plugins = {
+--       {
+--         name = "@vue/typescript-plugin",
+--         location = "/usr/local/lib/node_modules/@vue/typescript-plugin",
+--         languages = {"javascript", "typescript", "vue"},
+--       },
+--     },
+--   },
+--   filetypes = {
+--     "javascript",
+--     "typescript",
+--     "vue",
+--   },
+-- })
+--
+-- -- You must make sure volar is setup
+-- -- e.g. require'lspconfig'.volar.setup{}
+-- -- See volar's section for more information
+-- ```
+--
+-- `location` MUST be defined. If the plugin is installed in `node_modules`,
+-- `location` can have any value.
+--
+-- `languages` must include `vue` even if it is listed in `filetypes`.
+--
+-- `filetypes` is extended here to include Vue SFC.
+
+return {
+  init_options = { hostInfo = 'neovim' },
+  cmd = { 'typescript-language-server', '--stdio' },
+  filetypes = {
+    'javascript',
+    'javascriptreact',
+    'javascript.jsx',
+    'typescript',
+    'typescriptreact',
+    'typescript.tsx',
+  },
+  root_markers = { 'tsconfig.json', 'jsconfig.json', 'package.json', '.git' },
+}