mirror of
https://github.com/neovim/nvim-lspconfig.git
synced 2026-05-07 01:26:10 +02:00
fdfd9c2769
Problem: 78596b61 removed javascript.jsx and typescript.tsx from the lsp/ configs, but the same invalid filetypes remain in the legacy lua/lspconfig/configs/ files. These still surface in checkhealth warnings since the legacy configs get merged at runtime. Solution: remove javascript.jsx and typescript.tsx from all legacy config filetypes lists. The correct filetypes (javascriptreact, typescriptreact) are already present in each list.
93 lines
2.5 KiB
Lua
93 lines
2.5 KiB
Lua
-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|
-- This config is DEPRECATED.
|
|
-- Use the configs in `lsp/` instead (requires Nvim 0.11).
|
|
--
|
|
-- ALL configs in `lua/lspconfig/configs/` will be DELETED.
|
|
-- They exist only to support Nvim 0.10 or older.
|
|
-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|
local util = require 'lspconfig.util'
|
|
|
|
return {
|
|
default_config = {
|
|
init_options = { hostInfo = 'neovim' },
|
|
cmd = { 'typescript-language-server', '--stdio' },
|
|
filetypes = {
|
|
'javascript',
|
|
'javascriptreact',
|
|
'typescript',
|
|
'typescriptreact',
|
|
},
|
|
root_dir = util.root_pattern('tsconfig.json', 'jsconfig.json', 'package.json', '.git'),
|
|
single_file_support = true,
|
|
},
|
|
docs = {
|
|
description = [[
|
|
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
|
|
require'lspconfig'.ts_ls.setup{
|
|
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.
|
|
]],
|
|
},
|
|
}
|