generated: Updated lspconfig-servers.json

generated/lspconfig-servers.json

@@ -263,6 +263,7 @@
   "ruby_lsp": "https://shopify.github.io/ruby-lsp/ This gem is an implementation of the\nlanguage server protocol specification for Ruby, used to improve editor\nfeatures. Install the gem. There's no need to require it, since the\nserver is used as a standalone executable.\n\n``` sh\ngem install ruby-lsp\n```",
   "ruff": "https://github.com/astral-sh/ruff A Language Server Protocol\nimplementation for Ruff, an extremely fast Python linter and code\nformatter, written in Rust. It can be installed via `pip`.\n\n``` sh\npip install ruff\n```\n\n**Available in Ruff `v0.4.5` in beta and stabilized in Ruff `v0.5.3`.**\nThis is the new built-in language server written in Rust. It supports\nthe same feature set as `ruff-lsp`, but with superior performance and no\ninstallation required. Note that the `ruff-lsp` server will continue to\nbe maintained until further notice. Server settings can be provided via:\n\n``` lua\nvim.lsp.config('ruff', {\n  init_options = {\n    settings = {\n      -- Server settings should go here\n    }\n  }\n})\n```\n\nRefer to the [documentation](https://docs.astral.sh/ruff/editors/) for\nmore details.",
   "ruff_lsp": "https://github.com/astral-sh/ruff-lsp A Language Server Protocol\nimplementation for Ruff, an extremely fast Python linter and code\ntransformation tool, written in Rust. It can be installed via pip.\n\n``` sh\npip install ruff-lsp\n```\n\nExtra CLI arguments for `ruff` can be provided via\n\n``` lua\nvim.lsp.config('ruff_lsp', {\n  init_options = {\n    settings = {\n      -- Any extra CLI arguments for `ruff` go here.\n      args = {},\n    }\n  }\n})\n```",
+  "rumdl": "https://github.com/rvben/rumdl Markdown Linter and Formatter written in\nRust.",
   "rune_languageserver": "https://crates.io/crates/rune-languageserver A language server for the\n[Rune](https://rune-rs.github.io/) Language, an embeddable dynamic\nprogramming language for Rust",
   "rust_analyzer": "https://github.com/rust-lang/rust-analyzer rust-analyzer (aka rls 2.0),\na language server for Rust See\n[docs](https://rust-analyzer.github.io/book/configuration.html) for\nextra settings. The settings can be used like this:\n\n``` lua\nvim.lsp.config('rust_analyzer', {\n  settings = {\n    ['rust-analyzer'] = {\n      diagnostics = {\n        enable = false;\n      }\n    }\n  }\n})\n```\n\nNote: do not set `init_options` for this LS config, it will be\nautomatically populated by the contents of settings\\[\"rust-analyzer\"\\]\nper\nhttps://github.com/rust-lang/rust-analyzer/blob/eb5da56d839ae0a9e9f50774fa3eb78eb0964550/docs/dev/lsp-extensions.md?plain=1#L26.",
   "salt_ls": "Language server for Salt configuration files.\nhttps://github.com/dcermak/salt-lsp The language server can be installed\nwith `pip`:\n\n``` sh\npip install salt-lsp\n```",
@@ -327,7 +328,7 @@
   "tinymist": "https://github.com/Myriad-Dreamin/tinymist An integrated language\nservice for Typst \\[taɪpst\\]. You can also call it \"微霭\" \\[wēi ǎi\\] in\nChinese. Currently some of Tinymist's workspace commands are supported,\nnamely: `LspTinymistExportSvg`, `LspTinymistExportPng`,\n`LspTinymistExportPdf`, `LspTinymistExportMarkdown`,\n`LspTinymistExportText`, `LspTinymistExportQuery`,\n`LspTinymistExportAnsiHighlight`, `LspTinymistGetServerInfo`,\n`LspTinymistGetDocumentTrace`, `LspTinymistGetWorkspaceLabels`,\n`LspTinymistGetDocumentMetrics`, and `LspTinymistPinMain`.",
   "tofu_ls": "[OpenTofu Language Server](https://github.com/opentofu/tofu-ls)",
   "tombi": "https://tombi-toml.github.io/tombi/ Language server for Tombi, a TOML\ntoolkit.",
-  "ts_ls": "https://github.com/typescript-language-server/typescript-language-server\n`ts_ls`, aka `typescript-language-server`, is a Language Server Protocol\nimplementation for TypeScript wrapping `tsserver`. Note that `ts_ls` is\nnot `tsserver`. `typescript-language-server` depends on `typescript`.\nBoth packages can be installed via `npm`:\n\n``` sh\nnpm install -g typescript typescript-language-server\n```\n\nTo configure typescript language server, add a\n[`tsconfig.json`](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html)\nor\n[`jsconfig.json`](https://code.visualstudio.com/docs/languages/jsconfig)\nto the root of your project. Here's an example that disables type\nchecking in JavaScript files.\n\n``` json\n{\n  \"compilerOptions\": {\n    \"module\": \"commonjs\",\n    \"target\": \"es6\",\n    \"checkJs\": false\n  },\n  \"exclude\": [\n    \"node_modules\"\n  ]\n}\n```\n\nUse the `:LspTypescriptSourceAction` command to see \"whole file\"\n(\"source\") code-actions such as: - organize imports - remove unused code\n\\### Monorepo support `ts_ls` supports monorepos by default. It will\nautomatically find the `tsconfig.json` or `jsconfig.json` corresponding\nto the package you are working on. This works without the need of\nspawning multiple instances of `ts_ls`, saving memory. It is recommended\nto use the same version of TypeScript in all packages, and therefore\nhave it available in your workspace root. The location of the TypeScript\nbinary will be determined automatically, but only once.",
+  "ts_ls": "https://github.com/typescript-language-server/typescript-language-server\n`ts_ls`, aka `typescript-language-server`, is a Language Server Protocol\nimplementation for TypeScript wrapping `tsserver`. Note that `ts_ls` is\nnot `tsserver`. `typescript-language-server` depends on `typescript`.\nBoth packages can be installed via `npm`:\n\n``` sh\nnpm install -g typescript typescript-language-server\n```\n\nTo configure typescript language server, add a\n[`tsconfig.json`](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html)\nor\n[`jsconfig.json`](https://code.visualstudio.com/docs/languages/jsconfig)\nto the root of your project. Here's an example that disables type\nchecking in JavaScript files.\n\n``` json\n{\n  \"compilerOptions\": {\n    \"module\": \"commonjs\",\n    \"target\": \"es6\",\n    \"checkJs\": false\n  },\n  \"exclude\": [\n    \"node_modules\"\n  ]\n}\n```\n\nUse the `:LspTypescriptSourceAction` command to see \"whole file\"\n(\"source\") code-actions such as: - organize imports - remove unused code\nUse the `:LspTypescriptGoToSourceDefinition` command to navigate to the\nsource definition of a symbol (e.g., jump to the original implementation\ninstead of type definitions). \\### Monorepo support `ts_ls` supports\nmonorepos by default. It will automatically find the `tsconfig.json` or\n`jsconfig.json` corresponding to the package you are working on. This\nworks without the need of spawning multiple instances of `ts_ls`, saving\nmemory. It is recommended to use the same version of TypeScript in all\npackages, and therefore have it available in your workspace root. The\nlocation of the TypeScript binary will be determined automatically, but\nonly once.",
   "ts_query_ls": "https://github.com/ribru17/ts_query_ls Can be configured by passing a\n\"settings\" object to `vim.lsp.config('ts_query_ls', {})`:\n\n``` lua\nvim.lsp.config('ts_query_ls', {\n  init_options = {\n    parser_install_directories = {\n      '/my/parser/install/dir',\n    },\n    -- This setting is provided by default\n    parser_aliases = {\n      ecma = 'javascript',\n      jsx = 'javascript',\n      php_only = 'php',\n    },\n  },\n})\n```",
   "tsgo": "https://github.com/microsoft/typescript-go `typescript-go` is\nexperimental port of the TypeScript compiler (tsc) and language server\n(tsserver) to the Go programming language. `tsgo` can be installed via\nnpm `npm install @typescript/native-preview`. \\### Monorepo support\n`tsgo` supports monorepos by default. It will automatically find the\n`tsconfig.json` or `jsconfig.json` corresponding to the package you are\nworking on. This works without the need of spawning multiple instances\nof `tsgo`, saving memory. It is recommended to use the same version of\nTypeScript in all packages, and therefore have it available in your\nworkspace root. The location of the TypeScript binary will be determined\nautomatically, but only once.",
   "tsp_server": "https://github.com/microsoft/typespec The language server for TypeSpec,\na language for defining cloud service APIs and shapes. `tsp-server` can\nbe installed together with the typespec compiler via `npm`:\n\n``` sh\nnpm install -g @typespec/compiler\n```",
@@ -364,6 +365,7 @@
   "vtsls": "https://github.com/yioneko/vtsls `vtsls` can be installed with npm:\n\n``` sh\nnpm install -g @vtsls/language-server\n```\n\nTo configure a TypeScript project, add a\n[`tsconfig.json`](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html)\nor\n[`jsconfig.json`](https://code.visualstudio.com/docs/languages/jsconfig)\nto the root of your project. \\### Vue support Since v3.0.0, the Vue\nlanguage server requires `vtsls` to support TypeScript.\n\n    -- If you are using mason.nvim, you can get the ts_plugin_path like this\n    -- For Mason v1,\n    -- local mason_registry = require('mason-registry')\n    -- local vue_language_server_path = mason_registry.get_package('vue-language-server'):get_install_path() .. '/node_modules/@vue/language-server'\n    -- For Mason v2,\n    -- local vue_language_server_path = vim.fn.expand '$MASON/packages' .. '/vue-language-server' .. '/node_modules/@vue/language-server'\n    -- or even\n    -- local vue_language_server_path = vim.fn.stdpath('data') .. \"/mason/packages/vue-language-server/node_modules/@vue/language-server\"\n    local vue_language_server_path = '/path/to/@vue/language-server'\n    local vue_plugin = {\n      name = '@vue/typescript-plugin',\n      location = vue_language_server_path,\n      languages = { 'vue' },\n      configNamespace = 'typescript',\n    }\n    vim.lsp.config('vtsls', {\n      settings = {\n        vtsls = {\n          tsserver = {\n            globalPlugins = {\n              vue_plugin,\n            },\n          },\n        },\n      },\n      filetypes = { 'typescript', 'javascript', 'javascriptreact', 'typescriptreact', 'vue' },\n    })\n\n- `location` MUST be defined. If the plugin is installed in\n  `node_modules`, `location` can have any value.\n- `languages` must include vue even if it is listed in filetypes.\n- `filetypes` is extended here to include Vue SFC. You must make sure\n  the Vue language server is setup. For example,\n\n<!-- -->\n\n    vim.lsp.enable('vue_ls')\n\nSee `vue_ls` section and\nhttps://github.com/vuejs/language-tools/wiki/Neovim for more\ninformation. \\### Monorepo support `vtsls` supports monorepos by\ndefault. It will automatically find the `tsconfig.json` or\n`jsconfig.json` corresponding to the package you are working on. This\nworks without the need of spawning multiple instances of `vtsls`, saving\nmemory. It is recommended to use the same version of TypeScript in all\npackages, and therefore have it available in your workspace root. The\nlocation of the TypeScript binary will be determined automatically, but\nonly once.",
   "vue_ls": "https://github.com/vuejs/language-tools/tree/master/packages/language-server\nThe official language server for Vue It can be installed via npm:\n\n``` sh\nnpm install -g @vue/language-server\n```\n\nThe language server only supports Vue 3 projects by default. For Vue 2\nprojects, [additional\nconfiguration](https://github.com/vuejs/language-tools/blob/master/extensions/vscode/README.md?plain=1#L19)\nare required. The Vue language server works in \"hybrid mode\" that\nexclusively manages the CSS/HTML sections. You need the `vtsls` server\nwith the `@vue/typescript-plugin` plugin to support TypeScript in `.vue`\nfiles. See `vtsls` section and\nhttps://github.com/vuejs/language-tools/wiki/Neovim for more\ninformation. NOTE: Since v3.0.0, the Vue Language Server [no longer\nsupports takeover\nmode](https://github.com/vuejs/language-tools/pull/5248).",
   "wasm_language_tools": "https://github.com/g-plane/wasm-language-tools WebAssembly Language\nTools aims to provide and improve the editing experience of WebAssembly\nText Format. It also provides an out-of-the-box formatter (a.k.a. pretty\nprinter) for WebAssembly Text Format.",
+  "wc_language_server": "https://github.com/wc-toolkit/wc-language-server Web Components Language\nServer provides intelligent editor support for Web Components and custom\nelements. It offers advanced HTML diagnostics, completion, and\nvalidation for custom elements, including support for attribute types,\ndeprecation, and duplicate attribute detection. The language server uses\nthe [Custom Elements\nManifest](https://github.com/webcomponents/custom-elements-manifest) to\ngenerate component integration and validation information\n`wc-language-server` can be installed by following the instructions at\nthe [GitHub\nrepository](https://github.com/wc-toolkit/wc-language-server/blob/main/packages/neovim/README.md).\nThe default `cmd` assumes that the `wc-language-server` binary can be\nfound in `$PATH`. Alternatively, you can install it via\n[mason.nvim](https://github.com/williamboman/mason.nvim):\n\n``` vim\n:MasonInstall wc-language-server\n```\n\n**Configuration**\n\nThe language server reads settings from `wc.config.js` (or\n`.ts/.mjs/.cjs`) at the project root. Use it to customize manifest\nsources, file scoping, and diagnostic behavior. Example `wc.config.js`:\n\n``` js\nexport default {\n  // Fetch manifest from a custom path or URL\n  manifestSrc: './dist/custom-elements.json',\n  // Narrow which files opt into the language server\n  include: ['src/**/*.ts', 'src/**/*.html'],\n  // Skip specific globs\n  exclude: ['**/*.stories.ts'],\n  // Per-library overrides\n  libraries: {\n    '@your/pkg': {\n      manifestSrc: 'https://cdn.example.com/custom-elements.json',\n      tagFormatter: (tag) => tag.replace(/^x-/, 'my-'),\n    },\n  },\n  // Customize diagnostic severity levels\n  diagnosticSeverity: {\n    duplicateAttribute: 'warning',\n    unknownElement: 'info',\n  },\n};\n```\n\nSee the [configuration\ndocumentation](https://github.com/wc-toolkit/wc-language-server#configuration)\nfor more details.",
   "wgsl_analyzer": "https://github.com/wgsl-analyzer/wgsl-analyzer `wgsl-analyzer` can be\ninstalled via `cargo`:\n\n``` sh\ncargo install --git https://github.com/wgsl-analyzer/wgsl-analyzer wgsl-analyzer\n```",
   "yamlls": "https://github.com/redhat-developer/yaml-language-server\n`yaml-language-server` can be installed via `yarn`:\n\n``` sh\nyarn global add yaml-language-server\n```\n\nTo use a schema for validation, there are two options: 1. Add a modeline\nto the file. A modeline is a comment of the form:\n\n    # yaml-language-server: $schema=<urlToTheSchema|relativeFilePath|absoluteFilePath}>\n\nwhere the relative filepath is the path relative to the open yaml file,\nand the absolute filepath is the filepath relative to the filesystem\nroot ('/' on unix systems) 2. Associated a schema url, relative , or\nabsolute (to root of project, not to filesystem root) path to the a glob\npattern relative to the detected project root. Check\n`:checkhealth vim.lsp` to determine the resolved project root.\n\n``` lua\nvim.lsp.config('yamlls', {\n  ...\n  settings = {\n    yaml = {\n      ... -- other settings. note this overrides the lspconfig defaults.\n      schemas = {\n        [\"https://json.schemastore.org/github-workflow.json\"] = \"/.github/workflows/*\",\n        [\"../path/relative/to/file.yml\"] = \"/.github/workflows/*\",\n        [\"/path/from/root/of/project\"] = \"/.github/workflows/*\",\n      },\n    },\n  }\n})\n```\n\nCurrently, kubernetes is special-cased in yammls, see the following\nupstream issues: \\*\n[#211](https://github.com/redhat-developer/yaml-language-server/issues/211).\n\\*\n[#307](https://github.com/redhat-developer/yaml-language-server/issues/307).\nTo override a schema to use a specific k8s schema version (for example,\nto use 1.18):\n\n``` lua\nvim.lsp.config('yamlls', {\n  ...\n  settings = {\n    yaml = {\n      ... -- other settings. note this overrides the lspconfig defaults.\n      schemas = {\n        [\"https://raw.githubusercontent.com/yannh/kubernetes-json-schema/refs/heads/master/v1.32.1-standalone-strict/all.json\"] = \"/*.k8s.yaml\",\n        ... -- other schemas\n      },\n    },\n  }\n})\n```",
   "yang_lsp": "https://github.com/TypeFox/yang-lsp A Language Server for the YANG data\nmodeling language.",