RepoMirrors/nvim-lspconfig
1
0
Fork 0
mirror of https://github.com/neovim/nvim-lspconfig synced 2025-03-11 04:27:36 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
v1.6.0
nvim-lspconfig/doc/configs.md
github-actions[bot] bf81bef7d7 docs: update configs.md 
skip-checks: true
2025-01-29 16:07:58 +00:00

285 KiB
Raw Permalink Blame History

LSP configs

LSP configurations provided by nvim-lspconfig are listed below. This documentation is autogenerated from the Lua files. You can view this file in Nvim by running :help lspconfig-all.

ada_ls

https://github.com/AdaCore/ada_language_server

Installation instructions can be found here.

Can be configured by passing a "settings" object to ada_ls.setup{}:

require('lspconfig').ada_ls.setup{
    settings = {
      ada = {
        projectFile = "project.gpr";
        scenarioVariables = { ... };
      }
    }
}

Snippet to enable the language server:

require'lspconfig'.ada_ls.setup{}

Default config:

agda_ls

https://github.com/agda/agda-language-server

Language Server for Agda.

Snippet to enable the language server:

require'lspconfig'.agda_ls.setup{}

Default config:

aiken

https://github.com/aiken-lang/aiken

A language server for Aiken Programming Language. Installation

It can be i

Snippet to enable the language server:

require'lspconfig'.aiken.setup{}

Default config:

alloy_ls

https://github.com/AlloyTools/org.alloytools.alloy

Alloy is a formal specification language for describing structures and a tool for exploring them.

You may also need to configure the filetype for Alloy (*.als) files:

autocmd BufNewFile,BufRead *.als set filetype=alloy

or

vim.filetype.add({
  pattern = {
    ['.*/*.als'] = 'alloy',
  },
})

Alternatively, you may use a syntax plugin like https://github.com/runoshun/vim-alloy.

Snippet to enable the language server:

require'lspconfig'.alloy_ls.setup{}

Default config:

anakin_language_server

https://pypi.org/project/anakin-language-server/

anakin-language-server is yet another Jedi Python language server.

Available options:

Snippet to enable the language server:

require'lspconfig'.anakin_language_server.setup{}

Default config:

  • cmd : 
    { "anakinls" }
  • filetypes : 
    { "python" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/anakin_language_server.lua:4
  • settings : 
    {
  anakinls = {
    pyflakes_errors = { "ImportStarNotPermitted", "UndefinedExport", "UndefinedLocal", "UndefinedName", "DuplicateArgument", "MultiValueRepeatedKeyLiteral", "MultiValueRepeatedKeyVariable", "FutureFeatureNotDefined", "LateFutureImport", "ReturnOutsideFunction", "YieldOutsideFunction", "ContinueOutsideLoop", "BreakOutsideLoop", "TwoStarredExpressions", "TooManyExpressionsInStarredAssignment", "ForwardAnnotationSyntaxError", "RaiseNotImplemented", "StringDotFormatExtraPositionalArguments", "StringDotFormatExtraNamedArguments", "StringDotFormatMissingArgument", "StringDotFormatMixingAutomatic", "StringDotFormatInvalidFormat", "PercentFormatInvalidFormat", "PercentFormatMixedPositionalAndNamed", "PercentFormatUnsupportedFormat", "PercentFormatPositionalCountMismatch", "PercentFormatExtraNamedArguments", "PercentFormatMissingArgument", "PercentFormatExpectedMapping", "PercentFormatExpectedSequence", "PercentFormatStarRequiresSequence" }
  }
}
  • single_file_support : true

angularls

https://github.com/angular/vscode-ng-language-service

angular-language-server can be installed via npm npm install -g @angular/language-server.

Note, that if you override the default cmd, you must also update on_new_config to set new_config.cmd during startup.

local project_library_path = "/path/to/project/lib"
local cmd = {"ngserver", "--stdio", "--tsProbeLocations", project_library_path , "--ngProbeLocations", project_library_path}

require'lspconfig'.angularls.setup{
  cmd = cmd,
  on_new_config = function(new_config,new_root_dir)
    new_config.cmd = cmd
  end,
}

Snippet to enable the language server:

require'lspconfig'.angularls.setup{}

Default config:

  • cmd : 
    { "ngserver", "--stdio", "--tsProbeLocations", "", "--ngProbeLocations", "", "--angularCoreVersion", "" }
  • filetypes : 
    { "typescript", "html", "typescriptreact", "typescript.tsx", "htmlangular" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/angularls.lua:39

ansiblels

https://github.com/ansible/vscode-ansible

Language server for the ansible configuration management tool.

ansible-language-server can be installed via npm:

npm install -g @ansible/ansible-language-server

Snippet to enable the language server:

require'lspconfig'.ansiblels.setup{}

Default config:

  • cmd : 
    { "ansible-language-server", "--stdio" }
  • filetypes : 
    { "yaml.ansible" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/ansiblels.lua:4
  • settings : 
    {
  ansible = {
    ansible = {
      path = "ansible"
    },
    executionEnvironment = {
      enabled = false
    },
    python = {
      interpreterPath = "python"
    },
    validation = {
      enabled = true,
      lint = {
        enabled = true,
        path = "ansible-lint"
      }
    }
  }
}
  • single_file_support : true

antlersls

https://www.npmjs.com/package/antlers-language-server

antlersls can be installed via npm:

npm install -g antlers-language-server

Snippet to enable the language server:

require'lspconfig'.antlersls.setup{}

Default config:

apex_ls

https://github.com/forcedotcom/salesforcedx-vscode

Language server for Apex.

For manual installation, download the JAR file from the VSCode extension.

require'lspconfig'.apex_ls.setup {
  apex_jar_path = '/path/to/apex-jorje-lsp.jar',
  apex_enable_semantic_errors = false, -- Whether to allow Apex Language Server to surface semantic errors
  apex_enable_completion_statistics = false, -- Whether to allow Apex Language Server to collect telemetry on code completion usage
}

Snippet to enable the language server:

require'lspconfig'.apex_ls.setup{}

Default config:

arduino_language_server

https://github.com/arduino/arduino-language-server

Language server for Arduino

The arduino-language-server can be installed by running:

go install github.com/arduino/arduino-language-server@latest

The arduino-cli tool must also be installed. Follow these installation instructions for your platform.

After installing arduino-cli, follow these instructions for generating a configuration file if you haven't done so already, and make sure you install any relevant platforms libraries.

The language server also requires clangd to be installed. Follow these installation instructions for your platform.

If you don't have a sketch yet create one.

$ arduino-cli sketch new test
$ cd test

You will need a sketch.yaml file in order for the language server to understand your project. It will also save you passing options to arduino-cli each time you compile or upload a file. You can generate the file by using the following commands.

First gather some information about your board. Make sure your board is connected and run the following:

$ arduino-cli board list
Port         Protocol Type              Board Name  FQBN            Core
/dev/ttyACM0 serial   Serial Port (USB) Arduino Uno arduino:avr:uno arduino:avr

Then generate the file:

arduino-cli board attach -p /dev/ttyACM0 -b arduino:avr:uno test.ino

The resulting file should look like this:

default_fqbn: arduino:avr:uno
default_port: /dev/ttyACM0

Your folder structure should look like this:

.
├── test.ino
└── sketch.yaml

For further instructions about configuration options, run arduino-language-server --help.

Note that an upstream bug makes keywords in some cases become undefined by the language server. Ref: https://github.com/arduino/arduino-ide/issues/159

Snippet to enable the language server:

require'lspconfig'.arduino_language_server.setup{}

Default config:

asm_lsp

https://github.com/bergercookie/asm-lsp

Language Server for NASM/GAS/GO Assembly

asm-lsp can be installed via cargo: cargo install asm-lsp

Snippet to enable the language server:

require'lspconfig'.asm_lsp.setup{}

Default config:

ast_grep

https://ast-grep.github.io/

ast-grep(sg) is a fast and polyglot tool for code structural search, lint, rewriting at large scale. ast-grep LSP only works in projects that have sgconfig.y[a]ml in their root directories.

npm install [-g] @ast-grep/cli

Snippet to enable the language server:

require'lspconfig'.ast_grep.setup{}

Default config:

  • cmd : 
    { "ast-grep", "lsp" }
  • filetypes : 
    { "c", "cpp", "rust", "go", "java", "python", "javascript", "typescript", "html", "css", "kotlin", "dart", "lua" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/ast_grep.lua:4

astro

https://github.com/withastro/language-tools/tree/main/packages/language-server

astro-ls can be installed via npm:

npm install -g @astrojs/language-server

Snippet to enable the language server:

require'lspconfig'.astro.setup{}

Default config:

atlas

https://github.com/ariga/atlas

Language server for Atlas config and scheme files.

You may also need to configure the filetype for *.hcl files:

autocmd BufNewFile,BufRead atlas.hcl set filetype=atlas-config autocmd BufNewFile,BufRead *.my.hcl set filetype=atlas-schema-mysql autocmd BufNewFile,BufRead *.pg.hcl set filetype=atlas-schema-postgresql autocmd BufNewFile,BufRead *.lt.hcl set filetype=atlas-schema-sqlite autocmd BufNewFile,BufRead *.ch.hcl set filetype=atlas-schema-clickhouse autocmd BufNewFile,BufRead *.ms.hcl set filetype=atlas-schema-mssql autocmd BufNewFile,BufRead *.rs.hcl set filetype=atlas-schema-redshift autocmd BufNewFile,BufRead *.test.hcl set filetype=atlas-test autocmd BufNewFile,BufRead *.plan.hcl set filetype=atlas-plan

or

vim.filetype.add({
  filename = {
    ['atlas.hcl'] = 'atlas-config',
  },
  pattern = {
    ['.*/*.my.hcl'] = 'atlas-schema-mysql',
    ['.*/*.pg.hcl'] = 'atlas-schema-postgresql',
    ['.*/*.lt.hcl'] = 'atlas-schema-sqlite',
    ['.*/*.ch.hcl'] = 'atlas-schema-clickhouse',
    ['.*/*.ms.hcl'] = 'atlas-schema-mssql',
    ['.*/*.rs.hcl'] = 'atlas-schema-redshift',
    ['.*/*.test.hcl'] = 'atlas-test',
    ['.*/*.plan.hcl'] = 'atlas-plan',
  },
})

Snippet to enable the language server:

require'lspconfig'.atlas.setup{}

Default config:

autohotkey_lsp

https://github.com/thqby/vscode-autohotkey2-lsp

AutoHotkey v2.0 LSP implementation

Snippet to enable the language server:

require'lspconfig'.autohotkey_lsp.setup{}

Default config:

  • autostart : true
  • cmd : 
    { "autohotkey_lsp", "--stdio" }
  • filetypes : 
    { "autohotkey" }
  • flags : 
    {
  debounce_text_changes = 500
}
  • init_options : 
    {
  ActionWhenV1IsDetected = "Continue",
  AutoLibInclude = "All",
  CommentTags = "^;;\\s*(?<tag>.+)",
  CompleteFunctionParens = false,
  Diagnostics = {
    ClassStaticMemberCheck = true,
    ParamsCheck = true
  },
  FormatOptions = {
    array_style = "expand",
    brace_style = "One True Brace",
    break_chained_methods = false,
    ignore_comment = false,
    indent_string = "\t",
    max_preserve_newlines = 2,
    object_style = "none",
    preserve_newlines = true,
    space_after_double_colon = true,
    space_before_conditional = true,
    space_in_empty_paren = false,
    space_in_other = true,
    space_in_paren = false,
    wrap_line_length = 0
  },
  InterpreterPath = "",
  SymbolFoldinFromOpenBrace = false,
  locale = "en-us"
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/autohotkey_lsp.lua:8
  • single_file_support : true

autotools_ls

https://github.com/Freed-Wu/autotools-language-server

autotools-language-server can be installed via pip:

pip install autotools-language-server

Language server for autoconf, automake and make using tree sitter in python.

Snippet to enable the language server:

require'lspconfig'.autotools_ls.setup{}

Default config:

awk_ls

https://github.com/Beaglefoot/awk-language-server/

awk-language-server can be installed via npm:

npm install -g awk-language-server

Snippet to enable the language server:

require'lspconfig'.awk_ls.setup{}

Default config:

  • cmd : 
    { "awk-language-server" }
  • filetypes : 
    { "awk" }
  • single_file_support : true

azure_pipelines_ls

https://github.com/microsoft/azure-pipelines-language-server

An Azure Pipelines language server

azure-pipelines-ls can be installed via npm:

npm install -g azure-pipelines-language-server

By default azure-pipelines-ls will only work in files named azure-pipelines.yml, this can be changed by providing additional settings like so:

require("lspconfig").azure_pipelines_ls.setup {
  ... -- other configuration for setup {}
  settings = {
      yaml = {
          schemas = {
              ["https://raw.githubusercontent.com/microsoft/azure-pipelines-vscode/master/service-schema.json"] = {
                  "/azure-pipeline*.y*l",
                  "/*.azure*",
                  "Azure-Pipelines/**/*.y*l",
                  "Pipelines/*.y*l",
              },
          },
      },
  },
}

The Azure Pipelines LSP is a fork of yaml-language-server and as such the same settings can be passed to it as yaml-language-server.

Snippet to enable the language server:

require'lspconfig'.azure_pipelines_ls.setup{}

Default config:

bacon_ls

https://github.com/crisidev/bacon-ls

A Language Server Protocol wrapper for bacon. It offers textDocument/diagnostic and workspace/diagnostic capabilities for Rust workspaces using the Bacon export locations file.

It requires bacon and bacon-ls to be installed on the system using mason.nvim or manually:util

$ cargo install --locked bacon bacon-ls

Settings can be changed using the settings dictionary:util

settings = {
    -- Bacon export filename, default .bacon-locations
    locationsFile = ".bacon-locations",
    -- Maximum time in seconds the LSP server waits for Bacon to update the
    -- export file before loading the new diagnostics
    waitTimeSeconds = 10
}

Snippet to enable the language server:

require'lspconfig'.bacon_ls.setup{}

Default config:

ballerina

Ballerina language server

The Ballerina language's CLI tool comes with its own language server implementation. The bal command line tool must be installed and available in your system's PATH.

Snippet to enable the language server:

require'lspconfig'.ballerina.setup{}

Default config:

basedpyright

https://detachhead.github.io/basedpyright

basedpyright, a static type checker and language server for python

Snippet to enable the language server:

require'lspconfig'.basedpyright.setup{}

Commands:

  • PyrightOrganizeImports: Organize Imports
  • PyrightSetPythonPath: Reconfigure basedpyright with the provided python path

Default config:

  • cmd : 
    { "basedpyright-langserver", "--stdio" }
  • filetypes : 
    { "python" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/basedpyright.lua:44
  • settings : 
    {
  basedpyright = {
    analysis = {
      autoSearchPaths = true,
      diagnosticMode = "openFilesOnly",
      useLibraryCodeForTypes = true
    }
  }
}
  • single_file_support : true

bashls

https://github.com/bash-lsp/bash-language-server

bash-language-server can be installed via npm:

npm i -g bash-language-server

Language server for bash, written using tree sitter in typescript.

Snippet to enable the language server:

require'lspconfig'.bashls.setup{}

Default config:

  • cmd : 
    { "bash-language-server", "start" }
  • filetypes : 
    { "bash", "sh" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/bashls.lua:2
  • settings : 
    {
  bashIde = {
    globPattern = "*@(.sh|.inc|.bash|.command)"
  }
}
  • single_file_support : true

basics_ls

https://github.com/antonk52/basics-language-server/

Buffer, path, and snippet completion

npm install -g basics-language-server

Snippet to enable the language server:

require'lspconfig'.basics_ls.setup{}

Default config:

  • cmd : 
    { "basics-language-server" }
  • settings : 
    {
  buffer = {
    enable = true,
    minCompletionLength = 4
  },
  path = {
    enable = true
  },
  snippet = {
    enable = false,
    sources = {}
  }
}
  • single_file_support : true

bazelrc_lsp

https://github.com/salesforce-misc/bazelrc-lsp

bazelrc-lsp is a LSP for .bazelrc configuration files.

The .bazelrc file type is not detected automatically, you can register it manually (see below) or override the filetypes:

vim.filetype.add {
  pattern = {
    ['.*.bazelrc'] = 'bazelrc',
  },
}

Snippet to enable the language server:

require'lspconfig'.bazelrc_lsp.setup{}

Default config:

beancount

https://github.com/polarmutex/beancount-language-server#installation

See https://github.com/polarmutex/beancount-language-server#configuration for configuration options

Snippet to enable the language server:

require'lspconfig'.beancount.setup{}

Default config:

  • cmd : 
    { "beancount-language-server", "--stdio" }
  • filetypes : 
    { "beancount", "bean" }
  • init_options : 
    {}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/beancount.lua:2
  • single_file_support : true

bicep

https://github.com/azure/bicep Bicep language server

Bicep language server can be installed by downloading and extracting a release of bicep-langserver.zip from Bicep GitHub releases.

Bicep language server requires the dotnet-sdk to be installed.

Neovim does not have built-in support for the bicep filetype which is required for lspconfig to automatically launch the language server.

Filetype detection can be added via an autocmd:

vim.cmd [[ autocmd BufNewFile,BufRead *.bicep set filetype=bicep ]]

By default, bicep language server does not have a cmd set. This is because nvim-lspconfig does not make assumptions about your path. You must add the following to your init.vim or init.lua to set cmd to the absolute path ($HOME and ~ are not expanded) of the unzipped run script or binary.

local bicep_lsp_bin = "/path/to/bicep-langserver/Bicep.LangServer.dll"
require'lspconfig'.bicep.setup{
    cmd = { "dotnet", bicep_lsp_bin };
    ...
}

To download the latest release and place in /usr/local/bin/bicep-langserver:

(cd $(mktemp -d) \
    && curl -fLO https://github.com/Azure/bicep/releases/latest/download/bicep-langserver.zip \
    && rm -rf /usr/local/bin/bicep-langserver \
    && unzip -d /usr/local/bin/bicep-langserver bicep-langserver.zip)

Snippet to enable the language server:

require'lspconfig'.bicep.setup{}

Default config:

biome

https://biomejs.dev

Toolchain of the web. Successor of Rome.

npm install [-g] @biomejs/biome

Snippet to enable the language server:

require'lspconfig'.biome.setup{}

Default config:

  • cmd : 
    { "biome", "lsp-proxy" }
  • filetypes : 
    { "astro", "css", "graphql", "javascript", "javascriptreact", "json", "jsonc", "svelte", "typescript", "typescript.tsx", "typescriptreact", "vue" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/biome.lua:4
  • single_file_support : false

bitbake_language_server

🛠️ bitbake language server

Snippet to enable the language server:

require'lspconfig'.bitbake_language_server.setup{}

Default config:

bitbake_ls

https://github.com/yoctoproject/vscode-bitbake/tree/staging/server https://www.npmjs.com/package/language-server-bitbake

Official Bitbake Language Server for the Yocto Project.

Can be installed from npm or github.

npm install -g language-server-bitbake

Snippet to enable the language server:

require'lspconfig'.bitbake_ls.setup{}

Default config:

blueprint_ls

https://gitlab.gnome.org/jwestman/blueprint-compiler

blueprint-compiler can be installed via your system package manager.

Language server for the blueprint markup language, written in python and part of the blueprint-compiler.

Snippet to enable the language server:

require'lspconfig'.blueprint_ls.setup{}

Default config:

  • cmd : 
    { "blueprint-compiler", "lsp" }
  • cmd_env : 
    {
  GLOB_PATTERN = "*@(.blp)"
}
  • filetypes : 
    { "blueprint" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/blueprint_ls.lua:2
  • single_file_support : true

bqnlsp

https://git.sr.ht/~detegr/bqnlsp

bqnlsp, a language server for BQN.

The binary depends on the shared library of CBQN libcbqn.so. If CBQN is installed system-wide (using sudo make install in its source directory) and bqnlsp errors that it can't find the shared library, update the linker cache by executing sudo ldconfig. If CBQN has been installed in a non-standard directory or can't be installed globally pass libcbqnPath = '/path/to/CBQN' to the setup function. This will set the environment variables LD_LIBRARY_PATH (Linux) or DYLD_LIBRARY_PATH (macOS) to the provided path.

Snippet to enable the language server:

require'lspconfig'.bqnlsp.setup{}

Default config:

bright_script

https://github.com/RokuCommunity/brighterscript

brightscript can be installed via npm:

npm install -g brighterscript

Snippet to enable the language server:

require'lspconfig'.bright_script.setup{}

Default config:

bsl_ls

https://github.com/1c-syntax/bsl-language-server

Language Server Protocol implementation for 1C (BSL) - 1C:Enterprise 8 and OneScript languages.

Snippet to enable the language server:

require'lspconfig'.bsl_ls.setup{}

Default config:

buck2

https://github.com/facebook/buck2

Build system, successor to Buck

To better detect Buck2 project files, the following can be added:

vim.cmd [[ autocmd BufRead,BufNewFile *.bxl,BUCK,TARGETS set filetype=bzl ]]

Snippet to enable the language server:

require'lspconfig'.buck2.setup{}

Default config:

buddy_ls

https://github.com/buddy-compiler/buddy-mlir#buddy-lsp-server The Language Server for the buddy-mlir, a drop-in replacement for mlir-lsp-server, supporting new dialects defined in buddy-mlir. buddy-lsp-server can be installed at the buddy-mlir repository (buddy-compiler/buddy-mlir)

Snippet to enable the language server:

require'lspconfig'.buddy_ls.setup{}

Default config:

buf_ls

https://github.com/bufbuild/buf

buf beta lsp included in the cli itself

buf beta lsp is a Protobuf language server compatible with Buf modules and workspaces

Snippet to enable the language server:

require'lspconfig'.buf_ls.setup{}

Default config:

bufls

https://github.com/bufbuild/buf-language-server

buf-language-server can be installed via go install:

go install github.com/bufbuild/buf-language-server/cmd/bufls@latest

bufls is a Protobuf language server compatible with Buf modules and workspaces

Snippet to enable the language server:

require'lspconfig'.bufls.setup{}

Default config:

bzl

https://bzl.io/

https://docs.stack.build/docs/cli/installation

https://docs.stack.build/docs/vscode/starlark-language-server

Snippet to enable the language server:

require'lspconfig'.bzl.setup{}

Default config:

c3_lsp

https://github.com/pherrymason/c3-lsp

Language Server for c3.

Snippet to enable the language server:

require'lspconfig'.c3_lsp.setup{}

Default config:

cadence

Cadence Language Server using the flow-cli.

The flow command from flow-cli must be available. For install instructions see the docs or the Github page.

By default the configuration is taken from the closest flow.json or the flow.json in the users home directory.

Snippet to enable the language server:

require'lspconfig'.cadence.setup{}

Default config:

cairo_ls

Cairo Language Server

First, install Cairo following this tutorial

Then enable Cairo Language Server in your Lua configuration.

require'lspconfig'.cairo_ls.setup{}

cairo-language-server is still under active development, some features might not work yet !

Snippet to enable the language server:

require'lspconfig'.cairo_ls.setup{}

Default config:

  • cmd : 
    { "scarb-cairo-language-server", "/C", "--node-ipc" }
  • filetypes : 
    { "cairo" }
  • init_options : 
    {
  hostInfo = "neovim"
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/cairo_ls.lua:4

ccls

https://github.com/MaskRay/ccls/wiki

ccls relies on a JSON compilation database specified as compile_commands.json or, for simpler projects, a .ccls. For details on how to automatically generate one using CMake look here. Alternatively, you can use Bear.

Customization options are passed to ccls at initialization time via init_options, a list of available options can be found here. For example:

local lspconfig = require'lspconfig'
lspconfig.ccls.setup {
  init_options = {
    compilationDatabaseDirectory = "build";
    index = {
      threads = 0;
    };
    clang = {
      excludeArgs = { "-frounding-math"} ;
    };
  }
}

Snippet to enable the language server:

require'lspconfig'.ccls.setup{}

Commands:

  • CclsSwitchSourceHeader: Switch between source/header

Default config:

  • cmd : 
    { "ccls" }
  • filetypes : 
    { "c", "cpp", "objc", "objcpp", "cuda" }
  • offset_encoding : 
    "utf-32"
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/ccls.lua:24
  • single_file_support : false

cds_lsp

https://cap.cloud.sap/docs/

cds-lsp can be installed via npm:

npm i -g @sap/cds-lsp

Snippet to enable the language server:

require'lspconfig'.cds_lsp.setup{}

Default config:

  • cmd : 
    { "cds-lsp", "--stdio" }
  • filetypes : 
    { "cds" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/cds_lsp.lua:4
  • settings : 
    {
  cds = {
    validate = true
  }
}
  • single_file_support : true

circom-lsp

Circom Language Server

circom-lsp, the language server for the Circom language.

Snippet to enable the language server:

require'lspconfig'.circom-lsp.setup{}

Default config:

clangd

https://clangd.llvm.org/installation.html

Snippet to enable the language server:

require'lspconfig'.clangd.setup{}

Commands:

  • ClangdShowSymbolInfo: Show symbol info
  • ClangdSwitchSourceHeader: Switch between source/header

Default config:

  • capabilities : 
    {
  offsetEncoding = { "utf-8", "utf-16" },
  textDocument = {
    completion = {
      editsNearCursor = true
    }
  }
}
  • cmd : 
    { "clangd" }
  • filetypes : 
    { "c", "cpp", "objc", "objcpp", "cuda", "proto" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/clangd.lua:51
  • single_file_support : true

clarity_lsp

clarity-lsp is a language server for the Clarity language. Clarity is a decidable smart contract language that optimizes for predictability and security. Smart contracts allow developers to encode essential business logic on a blockchain.

To learn how to configure the clarity language server, see the clarity-lsp documentation.

Snippet to enable the language server:

require'lspconfig'.clarity_lsp.setup{}

Default config:

clojure_lsp

https://github.com/clojure-lsp/clojure-lsp

Clojure Language Server

Snippet to enable the language server:

require'lspconfig'.clojure_lsp.setup{}

Default config:

cmake

https://github.com/regen100/cmake-language-server

CMake LSP Implementation

Snippet to enable the language server:

require'lspconfig'.cmake.setup{}

Default config:

  • cmd : 
    { "cmake-language-server" }
  • filetypes : 
    { "cmake" }
  • init_options : 
    {
  buildDirectory = "build"
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/cmake.lua:4
  • single_file_support : true

cobol_ls

Cobol language support

Snippet to enable the language server:

require'lspconfig'.cobol_ls.setup{}

Default config:

codeqlls

Reference: https://codeql.github.com/docs/codeql-cli/

Binaries: https://github.com/github/codeql-cli-binaries

Snippet to enable the language server:

require'lspconfig'.codeqlls.setup{}

Default config:

coffeesense

https://github.com/phil294/coffeesense

CoffeeSense Language Server coffeesense-language-server can be installed via npm:

npm install -g coffeesense-language-server

Snippet to enable the language server:

require'lspconfig'.coffeesense.setup{}

Default config:

contextive

https://github.com/dev-cycles/contextive

Language Server for Contextive.

Contextive allows you to define terms in a central file and provides auto-completion suggestions and hover panels for these terms wherever they're used.

To install the language server, you need to download the appropriate GitHub release asset for your operating system and architecture.

After the download unzip the Contextive.LanguageServer binary and copy the file into a folder that is included in your system's PATH.

Snippet to enable the language server:

require'lspconfig'.contextive.setup{}

Default config:

coq_lsp

https://github.com/ejgallego/coq-lsp/

Snippet to enable the language server:

require'lspconfig'.coq_lsp.setup{}

Default config:

crystalline

https://github.com/elbywan/crystalline

Crystal language server.

Snippet to enable the language server:

require'lspconfig'.crystalline.setup{}

Default config:

csharp_ls

https://github.com/razzmatazz/csharp-language-server

Language Server for C#.

csharp-ls requires the dotnet-sdk to be installed.

The preferred way to install csharp-ls is with dotnet tool install --global csharp-ls.

Snippet to enable the language server:

require'lspconfig'.csharp_ls.setup{}

Default config:

css_variables

https://github.com/vunguyentuan/vscode-css-variables/tree/master/packages/css-variables-language-server

CSS variables autocompletion and go-to-definition

css-variables-language-server can be installed via npm:

npm i -g css-variables-language-server

Snippet to enable the language server:

require'lspconfig'.css_variables.setup{}

Default config:

  • cmd : 
    { "css-variables-language-server", "--stdio" }
  • filetypes : 
    { "css", "scss", "less" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/css_variables.lua:4
  • settings : 
    {
  cssVariables = {
    blacklistFolders = { "**/.cache", "**/.DS_Store", "**/.git", "**/.hg", "**/.next", "**/.svn", "**/bower_components", "**/CVS", "**/dist", "**/node_modules", "**/tests", "**/tmp" },
    lookupFiles = { "**/*.less", "**/*.scss", "**/*.sass", "**/*.css" }
  }
}

cssls

https://github.com/hrsh7th/vscode-langservers-extracted

css-languageserver can be installed via npm:

npm i -g vscode-langservers-extracted

Neovim does not currently include built-in snippets. vscode-css-language-server only provides completions when snippet support is enabled. To enable completion, install a snippet plugin and add the following override to your language client capabilities during setup.

--Enable (broadcasting) snippet capability for completion
local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities.textDocument.completion.completionItem.snippetSupport = true

require'lspconfig'.cssls.setup {
  capabilities = capabilities,
}

Snippet to enable the language server:

require'lspconfig'.cssls.setup{}

Default config:

  • cmd : 
    { "vscode-css-language-server", "--stdio" }
  • filetypes : 
    { "css", "scss", "less" }
  • init_options : 
    {
  provideFormatter = true
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/cssls.lua:4
  • settings : 
    {
  css = {
    validate = true
  },
  less = {
    validate = true
  },
  scss = {
    validate = true
  }
}
  • single_file_support : true

cssmodules_ls

https://github.com/antonk52/cssmodules-language-server

Language server for autocompletion and go-to-definition functionality for CSS modules.

You can install cssmodules-language-server via npm:

npm install -g cssmodules-language-server

Snippet to enable the language server:

require'lspconfig'.cssmodules_ls.setup{}

Default config:

cucumber_language_server

https://cucumber.io https://github.com/cucumber/common https://www.npmjs.com/package/@cucumber/language-server

Language server for Cucumber.

cucumber-language-server can be installed via npm:

npm install -g @cucumber/language-server

Snippet to enable the language server:

require'lspconfig'.cucumber_language_server.setup{}

Default config:

cue

https://github.com/cue-lang/cue

CUE makes it easy to validate data, write schemas, and ensure configurations align with policies.

Snippet to enable the language server:

require'lspconfig'.cue.setup{}

Default config:

custom_elements_ls

https://github.com/Matsuuu/custom-elements-language-server

custom-elements-languageserver depends on typescript. Both packages can be installed via npm:

npm install -g typescript custom-elements-languageserver

To configure typescript language server, add a tsconfig.json or jsconfig.json to the root of your project. Here's an example that disables type checking in JavaScript files.

{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es6",
    "checkJs": false
  },
  "exclude": [
    "node_modules"
  ]
}

Snippet to enable the language server:

require'lspconfig'.custom_elements_ls.setup{}

Default config:

cypher_ls

https://github.com/neo4j/cypher-language-support/tree/main/packages/language-server

cypher-language-server, language server for Cypher query language. Part of the umbrella project cypher-language-support: https://github.com/neo4j/cypher-language-support

cypher-language-server can be installed via npm:

npm i -g @neo4j-cypher/language-server

Snippet to enable the language server:

require'lspconfig'.cypher_ls.setup{}

Default config:

daedalus_ls

Snippet to enable the language server:

require'lspconfig'.daedalus_ls.setup{}

Default config:

  • cmd : 
    { "DaedalusLanguageServer" }
  • filetypes : 
    { "d" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/daedalus_ls.lua:14
  • settings : 
    {
  DaedalusLanguageServer = {
    fileEncoding = "Windows-1252",
    inlayHints = {
      constants = true
    },
    loglevel = "debug",
    numParserThreads = 16,
    srcFileEncoding = "Windows-1252"
  }
}

dafny

Support for the Dafny language server.

The default `cmd` uses "dafny server", which works on Dafny 4.0.0+. For
older versions of Dafny, you can compile the language server from source at
[dafny-lang/language-server-csharp](https://github.com/dafny-lang/language-server-csharp)
and set `cmd = {"dotnet", "<Path to your language server>"}`.

Snippet to enable the language server:

require'lspconfig'.dafny.setup{}

Default config:

dagger

https://github.com/dagger/cuelsp

Dagger's lsp server for cuelang.

Snippet to enable the language server:

require'lspconfig'.dagger.setup{}

Default config:

dartls

https://github.com/dart-lang/sdk/tree/master/pkg/analysis_server/tool/lsp_spec

Language server for dart.

Snippet to enable the language server:

require'lspconfig'.dartls.setup{}

Default config:

  • cmd : 
    { "dart", "language-server", "--protocol=lsp" }
  • filetypes : 
    { "dart" }
  • init_options : 
    {
  closingLabels = true,
  flutterOutline = true,
  onlyAnalyzeProjectsWithOpenFiles = true,
  outline = true,
  suggestFromUnimportedLibraries = true
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/dartls.lua:4
  • settings : 
    {
  dart = {
    completeFunctionCalls = true,
    showTodos = true
  }
}

dcmls

https://dcm.dev/

Language server for DCM analyzer.

Snippet to enable the language server:

require'lspconfig'.dcmls.setup{}

Default config:

debputy

https://salsa.debian.org/debian/debputy

Language Server for Debian packages.

Snippet to enable the language server:

require'lspconfig'.debputy.setup{}

Default config:

  • cmd : 
    { "debputy", "lsp", "server" }
  • filetypes : 
    { "debcontrol", "debcopyright", "debchangelog", "make", "yaml" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/debputy.lua:4

delphi_ls

Language server for Delphi from Embarcadero. https://marketplace.visualstudio.com/items?itemName=EmbarcaderoTechnologies.delphilsp

Note, the '*.delphilsp.json' file is required, more details at: https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Using_DelphiLSP_Code_Insight_with_Other_Editors

Below, you'll find a sample configuration for the lazy manager. When on_attach is triggered, it signals DelphiLSP to load settings from a configuration file. Without this step, DelphiLSP initializes but remains non-functional:

"neovim/nvim-lspconfig",
lazy = false,
config = function()
  local capabilities = require("cmp_nvim_lsp").default_capabilities()
  local lspconfig = require("lspconfig")

  lspconfig.delphi_ls.setup({
    capabilities = capabilities,

    on_attach = function(client)
      local lsp_config = vim.fs.find(function(name)
        return name:match(".*%.delphilsp.json$")
      end, { type = "file", path = client.config.root_dir, upward = false })[1]

      if lsp_config then
        client.config.settings = { settingsFile = lsp_config }
        client.notify("workspace/didChangeConfiguration", { settings = client.config.settings })
      else
        vim.notify_once("delphi_ls: '*.delphilsp.json' config file not found")
      end
    end,
  })
end,

Snippet to enable the language server:

require'lspconfig'.delphi_ls.setup{}

Default config:

denols

https://github.com/denoland/deno

Deno's built-in language server

To appropriately highlight codefences returned from denols, you will need to augment vim.g.markdown_fenced languages in your init.lua. Example:

vim.g.markdown_fenced_languages = {
  "ts=typescript"
}

Snippet to enable the language server:

require'lspconfig'.denols.setup{}

Commands:

  • DenolsCache: Cache a module and all of its dependencies.

Default config:

  • cmd : 
    { "deno", "lsp" }
  • cmd_env : 
    {
  NO_COLOR = true
}
  • filetypes : 
    { "javascript", "javascriptreact", "javascript.jsx", "typescript", "typescriptreact", "typescript.tsx" }
  • handlers : 
    {
  ["textDocument/definition"] = <function 1>,
  ["textDocument/references"] = <function 1>,
  ["textDocument/typeDefinition"] = <function 1>
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/denols.lua:66
  • settings : 
    {
  deno = {
    enable = true,
    suggest = {
      imports = {
        hosts = {
          ["https://deno.land"] = true
        }
      }
    }
  }
}

dhall_lsp_server

https://github.com/dhall-lang/dhall-haskell/tree/master/dhall-lsp-server

language server for dhall

dhall-lsp-server can be installed via cabal:

cabal install dhall-lsp-server

prebuilt binaries can be found here.

Snippet to enable the language server:

require'lspconfig'.dhall_lsp_server.setup{}

Default config:

diagnosticls

https://github.com/iamcco/diagnostic-languageserver

Diagnostic language server integrate with linters.

Snippet to enable the language server:

require'lspconfig'.diagnosticls.setup{}

Default config:

digestif

https://github.com/astoff/digestif

Digestif is a code analyzer, and a language server, for LaTeX, ConTeXt et caterva. It provides

context-sensitive completion, documentation, code navigation, and related functionality to any

text editor that speaks the LSP protocol.

Snippet to enable the language server:

require'lspconfig'.digestif.setup{}

Default config:

djlsp

https://github.com/fourdigits/django-template-lsp

  `djlsp`, a language server for Django templates.

Snippet to enable the language server:

require'lspconfig'.djlsp.setup{}

Default config:

docker_compose_language_service

https://github.com/microsoft/compose-language-service This project contains a language service for Docker Compose.

compose-language-service can be installed via npm:

npm install @microsoft/compose-language-service

Note: If the docker-compose-langserver doesn't startup when entering a docker-compose.yaml file, make sure that the filetype is yaml.docker-compose. You can set with: :set filetype=yaml.docker-compose.

Snippet to enable the language server:

require'lspconfig'.docker_compose_language_service.setup{}

Default config:

dockerls

https://github.com/rcjsuen/dockerfile-language-server-nodejs

docker-langserver can be installed via npm:

npm install -g dockerfile-language-server-nodejs

Additional configuration can be applied in the following way:

require("lspconfig").dockerls.setup {
    settings = {
        docker = {
	    languageserver = {
	        formatter = {
		    ignoreMultilineInstructions = true,
		},
	    },
	}
    }
}

Snippet to enable the language server:

require'lspconfig'.dockerls.setup{}

Default config:

dolmenls

https://github.com/Gbury/dolmen/blob/master/doc/lsp.md

dolmenls can be installed via opam

opam install dolmen_lsp

Snippet to enable the language server:

require'lspconfig'.dolmenls.setup{}

Default config:

dotls

https://github.com/nikeee/dot-language-server

dot-language-server can be installed via npm:

npm install -g dot-language-server

Snippet to enable the language server:

require'lspconfig'.dotls.setup{}

Default config:

dprint

https://github.com/dprint/dprint

Pluggable and configurable code formatting platform written in Rust.

Snippet to enable the language server:

require'lspconfig'.dprint.setup{}

Default config:

  • cmd : 
    { "dprint", "lsp" }
  • filetypes : 
    { "javascript", "javascriptreact", "typescript", "typescriptreact", "json", "jsonc", "markdown", "python", "toml", "rust", "roslyn", "graphql" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/dprint.lua:4
  • settings : 
    {}
  • single_file_support : true

drools_lsp

https://github.com/kiegroup/drools-lsp

Language server for the Drools Rule Language (DRL).

The drools-lsp server is a self-contained java jar file (drools-lsp-server-jar-with-dependencies.jar), and can be downloaded from https://github.com/kiegroup/drools-lsp/releases/.

Configuration information:

-- Option 1) Specify the entire command:
require('lspconfig').drools_lsp.setup {
  cmd = { '/path/to/java', '-jar', '/path/to/drools-lsp-server-jar-with-dependencies.jar' },
}

-- Option 2) Specify just the jar path (the JAVA_HOME environment variable will be respected if present):
require('lspconfig').drools_lsp.setup {
  drools = { jar = '/path/to/drools-lsp-server-jar-with-dependencies.jar' },
}

-- Option 3) Specify the java bin and/or java opts in addition to the jar path:
require('lspconfig').drools_lsp.setup {
  drools = {
    java = { bin = '/path/to/java', opts = { '-Xmx100m' } },
    jar = '/path/to/drools-lsp-server-jar-with-dependencies.jar',
  },
}

Neovim does not yet have automatic detection for the drools filetype, but it can be added with:

vim.cmd [[ autocmd BufNewFile,BufRead *.drl set filetype=drools ]]

Snippet to enable the language server:

require'lspconfig'.drools_lsp.setup{}

Default config:

ds_pinyin_lsp

https://github.com/iamcco/ds-pinyin-lsp Dead simple Pinyin language server for input Chinese without IME(input method). To install, download the latest release and ensure ds-pinyin-lsp is on your path. And make ensure the database file dict.db3 is also downloaded. And put the path to dict.dbs in the following code.


require('lspconfig').ds_pinyin_lsp.setup {
    init_options = {
        db_path = "your_path_to_database"
    }
}

Snippet to enable the language server:

require'lspconfig'.ds_pinyin_lsp.setup{}

Commands:

  • DsPinyinCompletionOff: Turn off the ds-pinyin-lsp completion
  • DsPinyinCompletionOn: Turn on the ds-pinyin-lsp completion

Default config:

  • cmd : 
    { "ds-pinyin-lsp" }
  • filetypes : 
    { "markdown", "org" }
  • init_options : 
    {
  completion_on = true,
  match_as_same_as_input = true,
  match_long_input = true,
  max_suggest = 15,
  show_symbols = true,
  show_symbols_by_n_times = 0,
  show_symbols_only_follow_by_hanzi = false
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/ds_pinyin_lsp.lua:33
  • single_file_support : true

earthlyls

https://github.com/glehmann/earthlyls

A fast language server for earthly.

Snippet to enable the language server:

require'lspconfig'.earthlyls.setup{}

Default config:

ecsact

https://github.com/ecsact-dev/ecsact_lsp_server

Language server for Ecsact.

The default cmd assumes ecsact_lsp_server is in your PATH. Typically from the Ecsact SDK: https://ecsact.dev/start

Snippet to enable the language server:

require'lspconfig'.ecsact.setup{}

Default config:

efm

https://github.com/mattn/efm-langserver

General purpose Language Server that can use specified error message format generated from specified command.

Requires at minimum EFM version v0.0.38 to support launching the language server on single files. If on an older version of EFM, disable single file support:

require('lspconfig')['efm'].setup{
  settings = ..., -- You must populate this according to the EFM readme
  filetypes = ..., -- Populate this according to the note below
  single_file_support = false, -- This is the important line for supporting older version of EFM
}

Note: In order for neovim's built-in language server client to send the appropriate languageId to EFM, you must specify filetypes in your call to setup{}. Otherwise lspconfig will launch EFM on the BufEnter instead of the FileType autocommand, and the filetype variable used to populate the languageId will not yet be set.

require('lspconfig')['efm'].setup{
  settings = ..., -- You must populate this according to the EFM readme
  filetypes = { 'python','cpp','lua' }
}

Snippet to enable the language server:

require'lspconfig'.efm.setup{}

Default config:

elixirls

https://github.com/elixir-lsp/elixir-ls

elixir-ls can be installed by following the instructions here.

  1. Download the zip from https://github.com/elixir-lsp/elixir-ls/releases/latest/
  2. Unzip it and make it executable. 
    unzip elixir-ls.zip -d /path/to/elixir-ls
# Unix
chmod +x /path/to/elixir-ls/language_server.sh

By default, elixir-ls doesn't have a cmd set. This is because nvim-lspconfig does not make assumptions about your path. You must add the following to your init.vim or init.lua to set cmd to the absolute path ($HOME and ~ are not expanded) of your unzipped elixir-ls.

require'lspconfig'.elixirls.setup{
    -- Unix
    cmd = { "/path/to/elixir-ls/language_server.sh" };
    -- Windows
    cmd = { "/path/to/elixir-ls/language_server.bat" };
    ...
}

'root_dir' is chosen like this: if two or more directories containing mix.exs were found when searching directories upward, the second one (higher up) is chosen, with the assumption that it is the root of an umbrella app. Otherwise the directory containing the single mix.exs that was found is chosen.

Snippet to enable the language server:

require'lspconfig'.elixirls.setup{}

Default config:

elmls

https://github.com/elm-tooling/elm-language-server#installation

If you don't want to use Nvim to install it, then you can use:

npm install -g elm elm-test elm-format @elm-tooling/elm-language-server

Snippet to enable the language server:

require'lspconfig'.elmls.setup{}

Default config:

  • capabilities : 
    {
  offsetEncoding = { "utf-8", "utf-16" }
}
  • cmd : 
    { "elm-language-server" }
  • filetypes : 
    { "elm" }
  • init_options : 
    {
  disableElmLSDiagnostics = false,
  elmReviewDiagnostics = "off",
  onlyUpdateDiagnosticsOnSave = false,
  skipInstallPackageConfirmation = false
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/elmls.lua:7

elp

https://whatsapp.github.io/erlang-language-platform

ELP integrates Erlang into modern IDEs via the language server protocol and was inspired by rust-analyzer.

Snippet to enable the language server:

require'lspconfig'.elp.setup{}

Default config:

ember

https://github.com/ember-tooling/ember-language-server

ember-language-server can be installed via npm:

npm install -g @ember-tooling/ember-language-server

Snippet to enable the language server:

require'lspconfig'.ember.setup{}

Default config:

  • cmd : 
    { "ember-language-server", "--stdio" }
  • filetypes : 
    { "handlebars", "typescript", "javascript", "typescript.glimmer", "javascript.glimmer" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/ember.lua:4

emmet_language_server

https://github.com/olrtg/emmet-language-server

Package can be installed via npm:

npm install -g @olrtg/emmet-language-server

Snippet to enable the language server:

require'lspconfig'.emmet_language_server.setup{}

Default config:

  • cmd : 
    { "emmet-language-server", "--stdio" }
  • filetypes : 
    { "css", "eruby", "html", "htmldjango", "javascriptreact", "less", "pug", "sass", "scss", "typescriptreact", "htmlangular" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/emmet_language_server.lua:2
  • single_file_support : true

emmet_ls

https://github.com/aca/emmet-ls

Package can be installed via npm:

npm install -g emmet-ls

Snippet to enable the language server:

require'lspconfig'.emmet_ls.setup{}

Default config:

  • cmd : 
    { "emmet-ls", "--stdio" }
  • filetypes : 
    { "astro", "css", "eruby", "html", "htmldjango", "javascriptreact", "less", "pug", "sass", "scss", "svelte", "typescriptreact", "vue", "htmlangular" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/emmet_ls.lua:2
  • single_file_support : true

erg_language_server

https://github.com/erg-lang/erg#flags ELS

ELS (erg-language-server) is a language server for the Erg programming language.

erg-language-server can be installed via cargo and used as follows:

cargo install erg --features els
erg --language-server

Snippet to enable the language server:

require'lspconfig'.erg_language_server.setup{}

Default config:

erlangls

https://erlang-ls.github.io

Language Server for Erlang.

Clone erlang_ls Compile the project with make and copy resulting binaries somewhere in your $PATH eg. cp _build/*/bin/* ~/local/bin

Installation instruction can be found here.

Installation requirements: - Erlang OTP 21+ - rebar3 3.9.1+

Snippet to enable the language server:

require'lspconfig'.erlangls.setup{}

Default config:

esbonio

https://github.com/swyddfa/esbonio

Esbonio is a language server for Sphinx documentation projects. The language server can be installed via pip

pip install esbonio

Since Sphinx is highly extensible you will get best results if you install the language server in the same Python environment as the one used to build your documentation. To ensure that the correct Python environment is picked up, you can either launch nvim with the correct environment activated.

source env/bin/activate
nvim

Or you can modify the default cmd to include the full path to the Python interpreter.

require'lspconfig'.esbonio.setup {
  cmd = { '/path/to/virtualenv/bin/python', '-m', 'esbonio' }
}

Esbonio supports a number of config values passed as init_options on startup, for example.

require'lspconfig'.esbonio.setup {
  init_options = {
    server = {
      logLevel = "debug"
    },
    sphinx = {
      confDir = "/path/to/docs",
      srcDir = "${confDir}/../docs-src"
    }
}

A full list and explanation of the available options can be found here

Snippet to enable the language server:

require'lspconfig'.esbonio.setup{}

Default config:

eslint

https://github.com/hrsh7th/vscode-langservers-extracted

vscode-eslint-language-server is a linting engine for JavaScript / Typescript. It can be installed via npm:

npm i -g vscode-langservers-extracted

vscode-eslint-language-server provides an EslintFixAll command that can be used to format a document on save:

lspconfig.eslint.setup({
  --- ...
  on_attach = function(client, bufnr)
    vim.api.nvim_create_autocmd("BufWritePre", {
      buffer = bufnr,
      command = "EslintFixAll",
    })
  end,
})

See vscode-eslint for configuration options.

Messages handled in lspconfig: eslint/openDoc, eslint/confirmESLintExecution, eslint/probeFailed, eslint/noLibrary

Additional messages you can handle: eslint/noConfig

Snippet to enable the language server:

require'lspconfig'.eslint.setup{}

Commands:

  • EslintFixAll: Fix all eslint problems for this buffer

Default config:

  • cmd : 
    { "vscode-eslint-language-server", "--stdio" }
  • filetypes : 
    { "javascript", "javascriptreact", "javascript.jsx", "typescript", "typescriptreact", "typescript.tsx", "vue", "svelte", "astro" }
  • handlers : 
    {
  ["eslint/confirmESLintExecution"] = <function 1>,
  ["eslint/noLibrary"] = <function 2>,
  ["eslint/openDoc"] = <function 3>,
  ["eslint/probeFailed"] = <function 4>
}
  • on_new_config source (use "gF" to visit): ../lua/lspconfig/configs/eslint.lua:51
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/eslint.lua:51
  • settings : 
    {
  codeAction = {
    disableRuleComment = {
      enable = true,
      location = "separateLine"
    },
    showDocumentation = {
      enable = true
    }
  },
  codeActionOnSave = {
    enable = false,
    mode = "all"
  },
  experimental = {
    useFlatConfig = false
  },
  format = true,
  nodePath = "",
  onIgnoredFiles = "off",
  problems = {
    shortenToSingleLine = false
  },
  quiet = false,
  rulesCustomizations = {},
  run = "onType",
  useESLintClass = false,
  validate = "on",
  workingDirectory = {
    mode = "location"
  }
}

facility_language_server

https://github.com/FacilityApi/FacilityLanguageServer

Facility language server protocol (LSP) support.

Snippet to enable the language server:

require'lspconfig'.facility_language_server.setup{}

Default config:

fennel_language_server

https://github.com/rydesun/fennel-language-server

Fennel language server protocol (LSP) support.

Snippet to enable the language server:

require'lspconfig'.fennel_language_server.setup{}

Default config:

fennel_ls

https://sr.ht/~xerool/fennel-ls/

A language server for fennel.

fennel-ls is configured using the closest file to your working directory named flsproject.fnl. All fennel-ls configuration options can be found here.

Snippet to enable the language server:

require'lspconfig'.fennel_ls.setup{}

Default config:

  • capabilities : 
    {
  offsetEncoding = { "utf-8", "utf-16" }
}
  • cmd : 
    { "fennel-ls" }
  • filetypes : 
    { "fennel" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/fennel_ls.lua:4
  • settings : 
    {}
  • single_file_support : true

fish_lsp

https://github.com/ndonfris/fish-lsp

A Language Server Protocol (LSP) tailored for the fish shell. This project aims to enhance the coding experience for fish, by introducing a suite of intelligent features like auto-completion, scope aware symbol analysis, per-token hover generation, and many others.

homepage

Snippet to enable the language server:

require'lspconfig'.fish_lsp.setup{}

Default config:

  • cmd : 
    { "fish-lsp", "start" }
  • cmd_env : 
    {
  fish_lsp_show_client_popups = false
}
  • filetypes : 
    { "fish" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/fish_lsp.lua:2
  • single_file_support : true

flow

https://flow.org/ https://github.com/facebook/flow

See below for how to setup Flow itself. https://flow.org/en/docs/install/

See below for lsp command options.

npx flow lsp --help

Snippet to enable the language server:

require'lspconfig'.flow.setup{}

Default config:

  • cmd : 
    { "npx", "--no-install", "flow", "lsp" }
  • filetypes : 
    { "javascript", "javascriptreact", "javascript.jsx" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/flow.lua:4

flux_lsp

https://github.com/influxdata/flux-lsp flux-lsp can be installed via cargo:

cargo install --git https://github.com/influxdata/flux-lsp

Snippet to enable the language server:

require'lspconfig'.flux_lsp.setup{}

Default config:

foam_ls

https://github.com/FoamScience/foam-language-server

foam-language-server can be installed via npm

npm install -g foam-language-server

Snippet to enable the language server:

require'lspconfig'.foam_ls.setup{}

Default config:

fortls

https://fortls.fortran-lang.org/index.html

fortls is a Fortran Language Server, the server can be installed via pip

pip install fortls

Settings to the server can be passed either through the cmd option or through a local configuration file e.g. .fortls. For more information see the fortls documentation.

Snippet to enable the language server:

require'lspconfig'.fortls.setup{}

Default config:

  • cmd : 
    { "fortls", "--notify_init", "--hover_signature", "--hover_language=fortran", "--use_signature_help" }
  • filetypes : 
    { "fortran" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/fortls.lua:4
  • settings : 
    {}

fsautocomplete

https://github.com/fsharp/FsAutoComplete

Language Server for F# provided by FsAutoComplete (FSAC).

FsAutoComplete requires the dotnet-sdk to be installed.

The preferred way to install FsAutoComplete is with dotnet tool install --global fsautocomplete.

Instructions to compile from source are found on the main repository.

You may also need to configure the filetype as Vim defaults to Forth for *.fs files:

autocmd BufNewFile,BufRead *.fs,*.fsx,*.fsi set filetype=fsharp

This is automatically done by plugins such as PhilT/vim-fsharp, fsharp/vim-fsharp, and adelarsq/neofsharp.vim.

Snippet to enable the language server:

require'lspconfig'.fsautocomplete.setup{}

Default config:

  • cmd : 
    { "fsautocomplete", "--adaptive-lsp-server-enabled" }
  • filetypes : 
    { "fsharp" }
  • init_options : 
    {
  AutomaticWorkspaceInit = true
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/fsautocomplete.lua:4
  • settings : 
    {
  FSharp = {
    EnableReferenceCodeLens = true,
    ExternalAutocomplete = false,
    InterfaceStubGeneration = true,
    InterfaceStubGenerationMethodBody = 'failwith "Not Implemented"',
    InterfaceStubGenerationObjectIdentifier = "this",
    Linter = true,
    RecordStubGeneration = true,
    RecordStubGenerationBody = 'failwith "Not Implemented"',
    ResolveNamespaces = true,
    SimplifyNameAnalyzer = true,
    UnionCaseStubGeneration = true,
    UnionCaseStubGenerationBody = 'failwith "Not Implemented"',
    UnusedDeclarationsAnalyzer = true,
    UnusedOpensAnalyzer = true,
    UseSdkScripts = true,
    keywordsAutocomplete = true
  }
}

fsharp_language_server

F# Language Server https://github.com/faldor20/fsharp-language-server

An implementation of the language server protocol using the F# Compiler Service.

Build the project from source and override the command path to location of DLL.

If filetype determination is not already performed by an available plugin (PhilT/vim-fsharp, fsharp/vim-fsharp, and adelarsq/neofsharp.vim. ), then the following must be added to initialization configuration:

autocmd BufNewFile,BufRead *.fs,*.fsx,*.fsi set filetype=fsharp

Snippet to enable the language server:

require'lspconfig'.fsharp_language_server.setup{}

Default config:

fstar

https://github.com/FStarLang/FStar

LSP support is included in FStar. Make sure fstar.exe is in your PATH.

Snippet to enable the language server:

require'lspconfig'.fstar.setup{}

Default config:

futhark_lsp

https://github.com/diku-dk/futhark

Futhark Language Server

This language server comes with the futhark compiler and is run with the command

futhark lsp

Snippet to enable the language server:

require'lspconfig'.futhark_lsp.setup{}

Default config:

gdscript

https://github.com/godotengine/godot

Language server for GDScript, used by Godot Engine.

Snippet to enable the language server:

require'lspconfig'.gdscript.setup{}

Default config:

gdshader_lsp

https://github.com/godofavacyn/gdshader-lsp

A language server for the Godot Shading language.

Snippet to enable the language server:

require'lspconfig'.gdshader_lsp.setup{}

Default config:

gh_actions_ls

https://github.com/lttb/gh-actions-language-server

Language server for GitHub Actions.

The projects forgejo and gitea design their actions to be as compatible to github as possible with only a few differences between the systems. The gh_actions_ls is therefore enabled for those yaml files as well.

The gh-actions-language-server can be installed via npm:

npm install -g gh-actions-language-server

Snippet to enable the language server:

require'lspconfig'.gh_actions_ls.setup{}

Default config:

  • capabilities : 
    {
  workspace = {
    didChangeWorkspaceFolders = {
      dynamicRegistration = true
    }
  }
}
  • cmd : 
    { "gh-actions-language-server", "--stdio" }
  • filetypes : 
    { "yaml" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/gh_actions_ls.lua:2
  • single_file_support : false

ghcide

https://github.com/digital-asset/ghcide

A library for building Haskell IDE tooling. "ghcide" isn't for end users now. Use "haskell-language-server" instead of "ghcide".

Snippet to enable the language server:

require'lspconfig'.ghcide.setup{}

Default config:

ghdl_ls

https://github.com/ghdl/ghdl-language-server

A language server for VHDL, using ghdl as its backend.

ghdl-ls is part of pyghdl, for installation instructions see the upstream README.

Snippet to enable the language server:

require'lspconfig'.ghdl_ls.setup{}

Default config:

ginko_ls

ginko_ls is meant to be a feature-complete language server for device-trees. Language servers can be used in many editors, such as Visual Studio Code, Emacs or Vim

Install ginko_ls from https://github.com/Schottkyc137/ginko and add it to path

ginko_ls doesn't require any configuration.

Snippet to enable the language server:

require'lspconfig'.ginko_ls.setup{}

Default config:

gitlab_ci_ls

https://github.com/alesbrelih/gitlab-ci-ls

Language Server for Gitlab CI

gitlab-ci-ls can be installed via cargo: cargo install gitlab-ci-ls

Snippet to enable the language server:

require'lspconfig'.gitlab_ci_ls.setup{}

Default config:

  • cmd : 
    { "gitlab-ci-ls" }
  • filetypes : 
    { "yaml.gitlab" }
  • init_options : 
    {
  cache_path = "/home/user/.cache/gitlab-ci-ls/",
  log_path = "/home/user/.cache/gitlab-ci-ls//log/gitlab-ci-ls.log"
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/gitlab_ci_ls.lua:5

glasgow

https://github.com/nolanderc/glasgow

Provides language features for WGSL (WebGPU Shading Language):

  • Completions:
    • Local functions/variables/types.
    • Fields and swizzles.
    • Builtin types and functions (dot, reflect, textureSample, vec3, mat4x2, etc.)
  • Hover Documentation:
    • Function signatures.
    • Variable types.
    • Includes builtin types and functions. Text is taken from the WGSL specification.
  • Goto Definition
  • Find all References
  • Rename
  • Formatter

glasgow can be installed via cargo:

cargo install glasgow

Snippet to enable the language server:

require'lspconfig'.glasgow.setup{}

Default config:

gleam

https://github.com/gleam-lang/gleam

A language server for Gleam Programming Language. Installation

It can be i

Snippet to enable the language server:

require'lspconfig'.gleam.setup{}

Default config:

glint

https://github.com/typed-ember/glint

https://typed-ember.gitbook.io/glint/

glint-language-server is installed when adding @glint/core to your project's devDependencies:

npm install @glint/core --save-dev

or

yarn add -D @glint/core

or

pnpm add -D @glint/core

Snippet to enable the language server:

require'lspconfig'.glint.setup{}

Default config:

glsl_analyzer

https://github.com/nolanderc/glsl_analyzer

Language server for GLSL

Snippet to enable the language server:

require'lspconfig'.glsl_analyzer.setup{}

Default config:

  • capabilities : 
    {}
  • cmd : 
    { "glsl_analyzer" }
  • filetypes : 
    { "glsl", "vert", "tesc", "tese", "frag", "geom", "comp" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/glsl_analyzer.lua:2
  • single_file_support : true

glslls

https://github.com/svenstaro/glsl-language-server

Language server implementation for GLSL

glslls can be compiled and installed manually, or, if your distribution has access to the AUR, via the glsl-language-server AUR package

Snippet to enable the language server:

require'lspconfig'.glslls.setup{}

Default config:

  • capabilities : 
    {
  offsetEncoding = { "utf-8", "utf-16" },
  textDocument = {
    completion = {
      editsNearCursor = true
    }
  }
}
  • cmd : 
    { "glslls", "--stdin" }
  • filetypes : 
    { "glsl", "vert", "tesc", "tese", "frag", "geom", "comp" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/glslls.lua:2
  • single_file_support : true

golangci_lint_ls

Combination of both lint server and client

https://github.com/nametake/golangci-lint-langserver https://github.com/golangci/golangci-lint

Installation of binaries needed is done via

go install github.com/nametake/golangci-lint-langserver@latest
go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest

Snippet to enable the language server:

require'lspconfig'.golangci_lint_ls.setup{}

Default config:

gopls

https://github.com/golang/tools/tree/master/gopls

Google's lsp server for golang.

Snippet to enable the language server:

require'lspconfig'.gopls.setup{}

Default config:

gradle_ls

https://github.com/microsoft/vscode-gradle

Microsoft's lsp server for gradle files

If you're setting this up manually, build vscode-gradle using ./gradlew installDist and point cmd to the gradle-language-server generated in the build directory

Snippet to enable the language server:

require'lspconfig'.gradle_ls.setup{}

Default config:

  • cmd : 
    { "gradle-language-server" }
  • filetypes : 
    { "groovy" }
  • init_options : 
    {
  settings = {
    gradleWrapperEnabled = true
  }
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/gradle_ls.lua:9

grammarly

https://github.com/znck/grammarly

grammarly-languageserver can be installed via npm:

npm i -g grammarly-languageserver

WARNING: Since this language server uses Grammarly's API, any document you open with it running is shared with them. Please evaluate their privacy policy before using this.

Snippet to enable the language server:

require'lspconfig'.grammarly.setup{}

Default config:

  • cmd : 
    { "grammarly-languageserver", "--stdio" }
  • filetypes : 
    { "markdown" }
  • handlers : 
    {
  ["$/updateDocumentState"] = <function 1>
}
  • init_options : 
    {
  clientId = "client_BaDkMgx4X19X9UxxYRCXZo"
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/grammarly.lua:2
  • single_file_support : true

graphql

https://github.com/graphql/graphiql/tree/main/packages/graphql-language-service-cli

graphql-lsp can be installed via npm:

npm install -g graphql-language-service-cli

Note that you must also have the graphql package installed within your project and create a GraphQL config file.

Snippet to enable the language server:

require'lspconfig'.graphql.setup{}

Default config:

  • cmd : 
    { "graphql-lsp", "server", "-m", "stream" }
  • filetypes : 
    { "graphql", "typescriptreact", "javascriptreact" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/graphql.lua:4

groovyls

https://github.com/prominic/groovy-language-server.git

Requirements:

  • Linux/macOS (for now)
  • Java 11+

groovyls can be installed by following the instructions here.

If you have installed groovy language server, you can set the cmd custom path as follow:

require'lspconfig'.groovyls.setup{
    -- Unix
    cmd = { "java", "-jar", "path/to/groovyls/groovy-language-server-all.jar" },
    ...
}

Snippet to enable the language server:

require'lspconfig'.groovyls.setup{}

Default config:

guile_ls

https://codeberg.org/rgherdt/scheme-lsp-server

The recommended way is to install guile-lsp-server is using Guix. Unfortunately it is still not available at the official Guix channels, but you can use the provided channel guix.scm in the repo:

guix package -f guix.scm

Checkout the repo for more info.

Note: This LSP will start on scheme.guile filetype. You can set this file type using :help modeline or adding https://gitlab.com/HiPhish/guile.vim to your plugins to automatically set it.

Snippet to enable the language server:

require'lspconfig'.guile_ls.setup{}

Default config:

harper_ls

https://github.com/elijah-potter/harper

The language server for Harper, the slim, clean language checker for developers.

See docs for more information on settings.

In short, however, they should look something like this:

lspconfig.harper_ls.setup {
  settings = {
    ["harper-ls"] = {
      userDictPath = "~/dict.txt"
    }
  },
}

Snippet to enable the language server:

require'lspconfig'.harper_ls.setup{}

Default config:

  • cmd : 
    { "harper-ls", "--stdio" }
  • filetypes : 
    { "c", "cpp", "cs", "gitcommit", "go", "html", "java", "javascript", "lua", "markdown", "nix", "python", "ruby", "rust", "swift", "toml", "typescript", "typescriptreact", "haskell", "cmake", "typst" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/harper_ls.lua:2
  • single_file_support : true

haxe_language_server

https://github.com/vshaxe/haxe-language-server

The Haxe language server can be built by running the following commands from the project's root directory:

npm install
npx lix run vshaxe-build -t language-server

This will create bin/server.js. Note that the server requires Haxe 3.4.0 or higher.

After building the language server, set the cmd setting in your setup function:

lspconfig.haxe_language_server.setup({
  cmd = {"node", "path/to/bin/server.js"},
})

By default, the language server is configured with the HXML compiler arguments contained in the first .hxml file found in your project's root directory. If you want to specify which one to use, set the init_options.displayArguments setting:

lspconfig.haxe_language_server.setup({
  -- ...
  init_options = {
    displayArguments = { "build.hxml" },
  },
})

Snippet to enable the language server:

require'lspconfig'.haxe_language_server.setup{}

Default config:

hdl_checker

https://github.com/suoto/hdl_checker Language server for hdl-checker. Install using: pip install hdl-checker --upgrade

Snippet to enable the language server:

require'lspconfig'.hdl_checker.setup{}

Default config:

helm_ls

https://github.com/mrjosh/helm-ls

Helm Language server. (This LSP is in early development)

helm Language server can be installed by following the instructions here.

The default cmd assumes that the helm_ls binary can be found in $PATH.

If need Helm file highlight use vim-helm plugin.

Snippet to enable the language server:

require'lspconfig'.helm_ls.setup{}

Default config:

  • capabilities : 
    {
  workspace = {
    didChangeWatchedFiles = {
      dynamicRegistration = true
    }
  }
}
  • cmd : 
    { "helm_ls", "serve" }
  • filetypes : 
    { "helm" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/helm_ls.lua:4
  • single_file_support : true

hhvm

Language server for programs written in Hack https://hhvm.com/ https://github.com/facebook/hhvm See below for how to setup HHVM & typechecker: https://docs.hhvm.com/hhvm/getting-started/getting-started

Snippet to enable the language server:

require'lspconfig'.hhvm.setup{}

Default config:

hie

https://github.com/haskell/haskell-ide-engine

the following init_options are supported (see https://github.com/haskell/haskell-ide-engine#configuration):

init_options = {
  languageServerHaskell = {
    hlintOn = bool;
    maxNumberOfProblems = number;
    diagnosticsDebounceDuration = number;
    liquidOn = bool (default false);
    completionSnippetsOn = bool (default true);
    formatOnImportOn = bool (default true);
    formattingProvider = string (default "brittany", alternate "floskell");
  }
}

Snippet to enable the language server:

require'lspconfig'.hie.setup{}

Default config:

hlasm

hlasm_language_server is a language server for the High Level Assembler language used on IBM SystemZ mainframes.

To learn how to configure the HLASM language server, see the [HLASM Language Support documentation](https://github.com/eclipse-che4z/che-che4z-lsp-for-hlasm).

Snippet to enable the language server:

require'lspconfig'.hlasm.setup{}

Default config:

hls

https://github.com/haskell/haskell-language-server

Haskell Language Server

If you are using HLS 1.9.0.0, enable the language server to launch on Cabal files as well:

require('lspconfig')['hls'].setup{
  filetypes = { 'haskell', 'lhaskell', 'cabal' },
}

Snippet to enable the language server:

require'lspconfig'.hls.setup{}

Default config:

  • cmd : 
    { "haskell-language-server-wrapper", "--lsp" }
  • filetypes : 
    { "haskell", "lhaskell" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/hls.lua:4
  • settings : 
    {
  haskell = {
    cabalFormattingProvider = "cabalfmt",
    formattingProvider = "ormolu"
  }
}
  • single_file_support : true

hoon_ls

https://github.com/urbit/hoon-language-server

A language server for Hoon.

The language server can be installed via npm install -g @hoon-language-server

Start a fake ~zod with urbit -F zod. Start the language server at the Urbit Dojo prompt with: |start %language-server

Snippet to enable the language server:

require'lspconfig'.hoon_ls.setup{}

Default config:

html

https://github.com/hrsh7th/vscode-langservers-extracted

vscode-html-language-server can be installed via npm:

npm i -g vscode-langservers-extracted

Neovim does not currently include built-in snippets. vscode-html-language-server only provides completions when snippet support is enabled. To enable completion, install a snippet plugin and add the following override to your language client capabilities during setup.

The code-formatting feature of the lsp can be controlled with the provideFormatter option.

--Enable (broadcasting) snippet capability for completion
local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities.textDocument.completion.completionItem.snippetSupport = true

require'lspconfig'.html.setup {
  capabilities = capabilities,
}

Snippet to enable the language server:

require'lspconfig'.html.setup{}

Default config:

  • cmd : 
    { "vscode-html-language-server", "--stdio" }
  • filetypes : 
    { "html", "templ" }
  • init_options : 
    {
  configurationSection = { "html", "css", "javascript" },
  embeddedLanguages = {
    css = true,
    javascript = true
  },
  provideFormatter = true
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/html.lua:4
  • settings : 
    {}
  • single_file_support : true

htmx

https://github.com/ThePrimeagen/htmx-lsp

htmx-lsp can be installed via cargo:

cargo install htmx-lsp

Lsp is still very much work in progress and experimental. Use at your own risk.

Snippet to enable the language server:

require'lspconfig'.htmx.setup{}

Default config:

  • cmd : 
    { "htmx-lsp" }
  • filetypes : 
    { "aspnetcorerazor", "astro", "astro-markdown", "blade", "clojure", "django-html", "htmldjango", "edge", "eelixir", "elixir", "ejs", "erb", "eruby", "gohtml", "gohtmltmpl", "haml", "handlebars", "hbs", "html", "htmlangular", "html-eex", "heex", "jade", "leaf", "liquid", "markdown", "mdx", "mustache", "njk", "nunjucks", "php", "razor", "slim", "twig", "javascript", "javascriptreact", "reason", "rescript", "typescript", "typescriptreact", "vue", "svelte", "templ" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/htmx.lua:2
  • single_file_support : true

hydra_lsp

https://github.com/Retsediv/hydra-lsp

LSP for Hydra Python package config files.

Snippet to enable the language server:

require'lspconfig'.hydra_lsp.setup{}

Default config:

hyprls

https://github.com/hyprland-community/hyprls

hyprls can be installed via go:

go install github.com/ewen-lbh/hyprls/cmd/hyprls@latest

Snippet to enable the language server:

require'lspconfig'.hyprls.setup{}

Default config:

idris2_lsp

https://github.com/idris-community/idris2-lsp

The Idris 2 language server.

Plugins for the Idris 2 filetype include Idris2-Vim (fewer features, stable) and Nvim-Idris2 (cutting-edge, experimental).

Idris2-Lsp requires a build of Idris 2 that includes the "Idris 2 API" package. Package managers with known support for this build include the AUR and Homebrew.

If your package manager does not support the Idris 2 API, you will need to build Idris 2 from source. Refer to the the Idris 2 installation instructions for details. Steps 5 and 8 are listed as "optional" in that guide, but they are necessary in order to make the Idris 2 API available.

You need to install a version of Idris2-Lsp that is compatible with your version of Idris 2. There should be a branch corresponding to every released Idris 2 version after v0.4.0. Use the latest commit on that branch. For example, if you have Idris v0.5.1, you should use the v0.5.1 branch of Idris2-Lsp.

If your Idris 2 version is newer than the newest Idris2-Lsp branch, use the latest commit on the master branch, and set a reminder to check the Idris2-Lsp repo for the release of a compatible versioned branch.

Snippet to enable the language server:

require'lspconfig'.idris2_lsp.setup{}

Default config:

intelephense

https://intelephense.com/

intelephense can be installed via npm:

npm install -g intelephense

-- See https://github.com/bmewburn/intelephense-docs/blob/master/installation.md#initialisation-options
init_options = {
  storagePath = …, -- Optional absolute path to storage dir. Defaults to os.tmpdir().
  globalStoragePath = …, -- Optional absolute path to a global storage dir. Defaults to os.homedir().
  licenceKey = …, -- Optional licence key or absolute path to a text file containing the licence key.
  clearCache = …, -- Optional flag to clear server state. State can also be cleared by deleting {storagePath}/intelephense
}
-- See https://github.com/bmewburn/intelephense-docs
settings = {
  intelephense = {
    files = {
      maxSize = 1000000;
    };
  };
}

Snippet to enable the language server:

require'lspconfig'.intelephense.setup{}

Default config:

janet_lsp

https://github.com/CFiggers/janet-lsp

A Language Server Protocol implementation for Janet.

Snippet to enable the language server:

require'lspconfig'.janet_lsp.setup{}

Default config:

java_language_server

https://github.com/georgewfraser/java-language-server

Java language server

Point cmd to lang_server_linux.sh or the equivalent script for macOS/Windows provided by java-language-server

Snippet to enable the language server:

require'lspconfig'.java_language_server.setup{}

Default config:

jdtls

https://projects.eclipse.org/projects/eclipse.jdt.ls

Language server for Java.

IMPORTANT: If you want all the features jdtls has to offer, nvim-jdtls is highly recommended. If all you need is diagnostics, completion, imports, gotos and formatting and some code actions you can keep reading here.

For manual installation you can download precompiled binaries from the official downloads site and ensure that the PATH variable contains the bin directory of the extracted archive.

  -- init.lua
  require'lspconfig'.jdtls.setup{}

You can also pass extra custom jvm arguments with the JDTLS_JVM_ARGS environment variable as a space separated list of arguments, that will be converted to multiple --jvm-arg= args when passed to the jdtls script. This will allow for example tweaking the jvm arguments or integration with external tools like lombok:

export JDTLS_JVM_ARGS="-javaagent:$HOME/.local/share/java/lombok.jar"

For automatic installation you can use the following unofficial installers/launchers under your own risk:

  • jdtls-launcher (Includes lombok support by default) 
      -- init.lua
  require'lspconfig'.jdtls.setup{ cmd = { 'jdtls' } }

Snippet to enable the language server:

require'lspconfig'.jdtls.setup{}

Default config:

  • cmd : 
    { "jdtls", "-configuration", "/home/user/.cache/jdtls/config", "-data", "/home/user/.cache/jdtls/workspace" }
  • filetypes : 
    { "java" }
  • handlers : 
    {
  ["language/status"] = <function 1>,
  ["textDocument/codeAction"] = <function 2>,
  ["textDocument/rename"] = <function 3>,
  ["workspace/applyEdit"] = <function 4>
}
  • init_options : 
    {
  jvm_args = {},
  workspace = "/home/user/.cache/jdtls/workspace"
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/jdtls.lua:80
  • single_file_support : true

jedi_language_server

https://github.com/pappasam/jedi-language-server

jedi-language-server, a language server for Python, built on top of jedi

Snippet to enable the language server:

require'lspconfig'.jedi_language_server.setup{}

Default config:

jinja_lsp

jinja-lsp enhances minijinja development experience by providing Helix/Nvim users with advanced features such as autocomplete, syntax highlighting, hover, goto definition, code actions and linting.

The file types are not detected automatically, you can register them manually (see below) or override the filetypes:

vim.filetype.add {
  extension = {
    jinja = 'jinja',
    jinja2 = 'jinja',
    j2 = 'jinja',
  },
}

Snippet to enable the language server:

require'lspconfig'.jinja_lsp.setup{}

Default config:

jqls

https://github.com/wader/jq-lsp Language server for jq, written using Go. You can install the server easily using go install:

# install directly
go install github.com/wader/jq-lsp@master
# copy binary to $PATH
cp $(go env GOPATH)/bin/jq-lsp /usr/local/bin

Note: To activate properly nvim needs to know the jq filetype. You can add it via:

vim.cmd([[au BufRead,BufNewFile *.jq setfiletype jq]])

Snippet to enable the language server:

require'lspconfig'.jqls.setup{}

Default config:

jsonls

https://github.com/hrsh7th/vscode-langservers-extracted

vscode-json-language-server, a language server for JSON and JSON schema

vscode-json-language-server can be installed via npm:

npm i -g vscode-langservers-extracted

vscode-json-language-server only provides completions when snippet support is enabled. If you use Neovim older than v0.10 you need to enable completion, install a snippet plugin and add the following override to your language client capabilities during setup.

--Enable (broadcasting) snippet capability for completion
local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities.textDocument.completion.completionItem.snippetSupport = true

require'lspconfig'.jsonls.setup {
  capabilities = capabilities,
}

Snippet to enable the language server:

require'lspconfig'.jsonls.setup{}

Default config:

  • cmd : 
    { "vscode-json-language-server", "--stdio" }
  • filetypes : 
    { "json", "jsonc" }
  • init_options : 
    {
  provideFormatter = true
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/jsonls.lua:2
  • single_file_support : true

jsonnet_ls

https://github.com/grafana/jsonnet-language-server

A Language Server Protocol (LSP) server for Jsonnet.

The language server can be installed with go:

go install github.com/grafana/jsonnet-language-server@latest

Snippet to enable the language server:

require'lspconfig'.jsonnet_ls.setup{}

Default config:

julials

https://github.com/julia-vscode/julia-vscode

LanguageServer.jl can be installed with julia and Pkg:

julia --project=~/.julia/environments/nvim-lspconfig -e 'using Pkg; Pkg.add("LanguageServer")'

where ~/.julia/environments/nvim-lspconfig is the location where the default configuration expects LanguageServer.jl to be installed.

To update an existing install, use the following command:

julia --project=~/.julia/environments/nvim-lspconfig -e 'using Pkg; Pkg.update()'

Note: In order to have LanguageServer.jl pick up installed packages or dependencies in a Julia project, you must make sure that the project is instantiated:

julia --project=/path/to/my/project -e 'using Pkg; Pkg.instantiate()'

Note: The julia programming language searches for global environments within the environments/ folder of $JULIA_DEPOT_PATH entries. By default this simply ~/.julia/environments

Snippet to enable the language server:

require'lspconfig'.julials.setup{}

Commands:

  • JuliaActivateEnv: Activate a Julia environment

Default config:

  • cmd : 
    { "julia", "--startup-file=no", "--history-file=no", "-e", '    # Load LanguageServer.jl: attempt to load from ~/.julia/environments/nvim-lspconfig\n    # with the regular load path as a fallback\n    ls_install_path = joinpath(\n        get(DEPOT_PATH, 1, joinpath(homedir(), ".julia")),\n        "environments", "nvim-lspconfig"\n    )\n    pushfirst!(LOAD_PATH, ls_install_path)\n    using LanguageServer\n    popfirst!(LOAD_PATH)\n    depot_path = get(ENV, "JULIA_DEPOT_PATH", "")\n    project_path = let\n        dirname(something(\n            ## 1. Finds an explicitly set project (JULIA_PROJECT)\n            Base.load_path_expand((\n                p = get(ENV, "JULIA_PROJECT", nothing);\n                p === nothing ? nothing : isempty(p) ? nothing : p\n            )),\n            ## 2. Look for a Project.toml file in the current working directory,\n            ##    or parent directories, with $HOME as an upper boundary\n            Base.current_project(),\n            ## 3. First entry in the load path\n            get(Base.load_path(), 1, nothing),\n            ## 4. Fallback to default global environment,\n            ##    this is more or less unreachable\n            Base.load_path_expand("@v#.#"),\n        ))\n    end\n    @info "Running language server" VERSION pwd() project_path depot_path\n    server = LanguageServer.LanguageServerInstance(stdin, stdout, project_path, depot_path)\n    server.runlinter = true\n    run(server)\n  ' }
  • filetypes : 
    { "julia" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/julials.lua:97
  • single_file_support : true

kcl

https://github.com/kcl-lang/kcl.nvim

Language server for the KCL configuration and policy language.

Snippet to enable the language server:

require'lspconfig'.kcl.setup{}

Default config:

koka

https://koka-lang.github.io/koka/doc/index.html Koka is a functional programming language with effect types and handlers.

Snippet to enable the language server:

require'lspconfig'.koka.setup{}

Default config:

  • cmd : 
    { "koka", "--language-server", "--lsstdio" }
  • filetypes : 
    { "koka" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/koka.lua:2
  • single_file_support : true

kotlin_language_server

A kotlin language server which was developed for internal usage and released afterwards. Maintaining is not done by the original author, but by fwcd.

It is built via gradle and developed on github.
Source and additional description:
https://github.com/fwcd/kotlin-language-server

This server requires vim to be aware of the kotlin-filetype.
You could refer for this capability to:
https://github.com/udalov/kotlin-vim (recommended)
Note that there is no LICENSE specified yet.

For faster startup, you can setup caching by specifying a storagePath
in the init_options. The default is your home directory.

Snippet to enable the language server:

require'lspconfig'.kotlin_language_server.setup{}

Default config:

kulala_ls

https://github.com/mistweaverco/kulala-ls

A minimal language server for HTTP syntax.

Snippet to enable the language server:

require'lspconfig'.kulala_ls.setup{}

Default config:

lean3ls

https://github.com/leanprover/lean-client-js/tree/master/lean-language-server

Lean installation instructions can be found here.

Once Lean is installed, you can install the Lean 3 language server by running

npm install -g lean-language-server

Note: that if you're using lean.nvim, that plugin fully handles the setup of the Lean language server, and you shouldn't set up lean3ls both with it and lspconfig.

Snippet to enable the language server:

require'lspconfig'.lean3ls.setup{}

Default config:

  • cmd : 
    { "lean-language-server", "--stdio", "--", "-M", "4096", "-T", "100000" }
  • filetypes : 
    { "lean3" }
  • offset_encoding : 
    "utf-32"
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/lean3ls.lua:4
  • single_file_support : true

leanls

https://github.com/leanprover/lean4

Lean installation instructions can be found here.

The Lean language server is included in any Lean installation and does not require any additional packages.

Note: that if you're using lean.nvim, that plugin fully handles the setup of the Lean language server, and you shouldn't set up leanls both with it and lspconfig.

Snippet to enable the language server:

require'lspconfig'.leanls.setup{}

Default config:

lelwel_ls

https://github.com/0x2a-42/lelwel

Language server for lelwel grammars.

You can install lelwel-ls via cargo:

cargo install --features="lsp" lelwel

Snippet to enable the language server:

require'lspconfig'.lelwel_ls.setup{}

Default config:

lemminx

https://github.com/eclipse/lemminx

The easiest way to install the server is to get a binary from https://github.com/redhat-developer/vscode-xml/releases and place it on your PATH.

NOTE to macOS users: Binaries from unidentified developers are blocked by default. If you trust the downloaded binary, run it once, cancel the prompt, then remove the binary from Gatekeeper quarantine with xattr -d com.apple.quarantine lemminx. It should now run without being blocked.

Snippet to enable the language server:

require'lspconfig'.lemminx.setup{}

Default config:

lexical

https://github.com/lexical-lsp/lexical

Lexical is a next-generation language server for the Elixir programming language.

Follow the Detailed Installation Instructions

By default, lexical doesn't have a cmd set. This is because nvim-lspconfig does not make assumptions about your path.

Snippet to enable the language server:

require'lspconfig'.lexical.setup{}

Default config:

lsp_ai

https://github.com/SilasMarvin/lsp-ai

LSP-AI is an open source language server that serves as a backend for AI-powered functionality in your favorite code editors. It offers features like in-editor chatting with LLMs and code completions.

You will need to provide configuration for the inference backends and models you want to use, as well as configure completion/code actions. See the wiki docs and examples for more information.

Snippet to enable the language server:

require'lspconfig'.lsp_ai.setup{}

Default config:

  • cmd : 
    { "lsp-ai" }
  • filetypes : 
    {}
  • init_options : 
    {
  memory = {
    file_store = vim.empty_dict()
  },
  models = vim.empty_dict()
}
  • single_file_support : true

ltex

https://github.com/valentjn/ltex-ls

LTeX Language Server: LSP language server for LanguageTool 🔍✔️ with support for LaTeX 🎓, Markdown 📝, and others

To install, download the latest release and ensure ltex-ls is on your path.

This server accepts configuration via the settings key.

  settings = {
		ltex = {
			language = "en-GB",
		},
	},

To support org files or R sweave, users can define a custom filetype autocommand (or use a plugin which defines these filetypes):

vim.cmd [[ autocmd BufRead,BufNewFile *.org set filetype=org ]]

Snippet to enable the language server:

require'lspconfig'.ltex.setup{}

Default config:

  • cmd : 
    { "ltex-ls" }
  • filetypes : 
    { "bib", "gitcommit", "markdown", "org", "plaintex", "rst", "rnoweb", "tex", "pandoc", "quarto", "rmd", "context", "html", "xhtml", "mail", "text" }
  • get_language_id source (use "gF" to visit): ../lua/lspconfig/configs/ltex.lua:51
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/ltex.lua:51
  • settings : 
    {
  ltex = {
    enabled = { "bibtex", "gitcommit", "markdown", "org", "tex", "restructuredtext", "rsweave", "latex", "quarto", "rmd", "context", "html", "xhtml", "mail", "plaintext" }
  }
}
  • single_file_support : true

ltex_plus

https://github.com/ltex-plus/ltex-ls-plus

LTeX Language Server: LSP language server for LanguageTool 🔍✔️ with support for LaTeX 🎓, Markdown 📝, and others

To install, download the latest release and ensure ltex-ls-plus is on your path.

This server accepts configuration via the settings key.

  settings = {
    ltex = {
      language = "en-GB",
    },
  },

To support org files or R sweave, users can define a custom filetype autocommand (or use a plugin which defines these filetypes):

vim.cmd [[ autocmd BufRead,BufNewFile *.org set filetype=org ]]

Snippet to enable the language server:

require'lspconfig'.ltex_plus.setup{}

Default config:

  • cmd : 
    { "ltex-ls-plus" }
  • filetypes : 
    { "bib", "context", "gitcommit", "html", "markdown", "org", "pandoc", "plaintex", "quarto", "mail", "mdx", "rmd", "rnoweb", "rst", "tex", "text", "typst", "xhtml" }
  • get_language_id source (use "gF" to visit): ../lua/lspconfig/configs/ltex_plus.lua:16
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/ltex_plus.lua:16
  • settings : 
    {
  ltex = {
    enabled = { "bib", "context", "gitcommit", "html", "markdown", "org", "pandoc", "plaintex", "quarto", "mail", "mdx", "rmd", "rnoweb", "rst", "tex", "text", "typst", "xhtml" }
  }
}
  • single_file_support : true

lua_ls

https://github.com/luals/lua-language-server

Lua language server.

lua-language-server can be installed by following the instructions here.

The default cmd assumes that the lua-language-server binary can be found in $PATH.

If you primarily use lua-language-server for Neovim, and want to provide completions, analysis, and location handling for plugins on runtime path, you can use the following settings.

require'lspconfig'.lua_ls.setup {
  on_init = function(client)
    if client.workspace_folders then
      local path = client.workspace_folders[1].name
      if vim.loop.fs_stat(path..'/.luarc.json') or vim.loop.fs_stat(path..'/.luarc.jsonc') then
        return
      end
    end

    client.config.settings.Lua = vim.tbl_deep_extend('force', client.config.settings.Lua, {
      runtime = {
        -- Tell the language server which version of Lua you're using
        -- (most likely LuaJIT in the case of Neovim)
        version = 'LuaJIT'
      },
      -- Make the server aware of Neovim runtime files
      workspace = {
        checkThirdParty = false,
        library = {
          vim.env.VIMRUNTIME
          -- Depending on the usage, you might want to add additional paths here.
          -- "${3rd}/luv/library"
          -- "${3rd}/busted/library",
        }
        -- or pull in all of 'runtimepath'. NOTE: this is a lot slower and will cause issues when working on your own configuration (see https://github.com/neovim/nvim-lspconfig/issues/3189)
        -- library = vim.api.nvim_get_runtime_file("", true)
      }
    })
  end,
  settings = {
    Lua = {}
  }
}

See lua-language-server's documentation for an explanation of the above fields:

Snippet to enable the language server:

require'lspconfig'.lua_ls.setup{}

Default config:

luau_lsp

Snippet to enable the language server:

require'lspconfig'.luau_lsp.setup{}

Default config:

lwc_ls

https://github.com/forcedotcom/lightning-language-server/

Language server for Lightning Web Components.

For manual installation, utilize the official NPM package. Then, configure cmd to run the Node script at the unpacked location:

require'lspconfig'.lwc_ls.setup {
  cmd = {
    'node',
    '/path/to/node_modules/@salesforce/lwc-language-server/bin/lwc-language-server.js',
    '--stdio'
  }
}

Snippet to enable the language server:

require'lspconfig'.lwc_ls.setup{}

Default config:

  • cmd : 
    { "lwc-language-server", "--stdio" }
  • filetypes : 
    { "javascript", "html" }
  • init_options : 
    {
  embeddedLanguages = {
    javascript = true
  }
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/lwc_ls.lua:4

m68k

https://github.com/grahambates/m68k-lsp

Language server for Motorola 68000 family assembly

m68k-lsp-server can be installed via npm:

npm install -g m68k-lsp-server

Ensure you are using the 68k asm syntax variant in Neovim.

vim.g.asmsyntax = 'asm68k'

Snippet to enable the language server:

require'lspconfig'.m68k.setup{}

Default config:

markdown_oxide

https://github.com/Feel-ix-343/markdown-oxide

Editor Agnostic PKM: you bring the text editor and we bring the PKM.

Inspired by and compatible with Obsidian.

Check the readme to see how to properly setup.

Snippet to enable the language server:

require'lspconfig'.markdown_oxide.setup{}

Commands:

  • Today: Open today's daily note
  • Tomorrow: Open tomorrow's daily note
  • Yesterday: Open yesterday's daily note

Default config:

marko-js

https://github.com/marko-js/language-server

  Using the Language Server Protocol to improve Marko's developer experience.

  Can be installed via npm:
  ```
  npm i -g @marko/language-server
  ```

Snippet to enable the language server:

require'lspconfig'.marko-js.setup{}

Default config:

marksman

https://github.com/artempyanykh/marksman

Marksman is a Markdown LSP server providing completion, cross-references, diagnostics, and more.

Marksman works on MacOS, Linux, and Windows and is distributed as a self-contained binary for each OS.

Pre-built binaries can be downloaded from https://github.com/artempyanykh/marksman/releases

Snippet to enable the language server:

require'lspconfig'.marksman.setup{}

Default config:

matlab_ls

https://github.com/mathworks/MATLAB-language-server

MATLAB® language server implements the Microsoft® Language Server Protocol for the MATLAB language.

Snippet to enable the language server:

require'lspconfig'.matlab_ls.setup{}

Default config:

  • cmd : 
    { "matlab-language-server", "--stdio" }
  • filetypes : 
    { "matlab" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/matlab_ls.lua:2
  • settings : 
    {
  MATLAB = {
    indexWorkspace = false,
    installPath = "",
    matlabConnectionTiming = "onStart",
    telemetry = true
  }
}
  • single_file_support : false

mdx_analyzer

https://github.com/mdx-js/mdx-analyzer

mdx-analyzer, a language server for MDX

Snippet to enable the language server:

require'lspconfig'.mdx_analyzer.setup{}

Default config:

mesonlsp

https://github.com/JCWasmx86/mesonlsp

An unofficial, unendorsed language server for meson written in C++

Snippet to enable the language server:

require'lspconfig'.mesonlsp.setup{}

Default config:

metals

https://scalameta.org/metals/

Scala language server with rich IDE features.

See full instructions in the Metals documentation:

https://scalameta.org/metals/docs/editors/vim#using-an-alternative-lsp-client

Note: that if you're using nvim-metals, that plugin fully handles the setup and installation of Metals, and you shouldn't set up Metals both with it and lspconfig.

To install Metals, make sure to have coursier installed, and once you do you can install the latest Metals with cs install metals.

Snippet to enable the language server:

require'lspconfig'.metals.setup{}

Default config:

  • capabilities : 
    {
  workspace = {
    configuration = false
  }
}
  • cmd : 
    { "metals" }
  • filetypes : 
    { "scala" }
  • init_options : 
    {
  compilerOptions = {
    snippetAutoIndent = false
  },
  isHttpEnabled = true,
  statusBarProvider = "show-message"
}
  • message_level : 
    4
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/metals.lua:4

millet

https://github.com/azdavis/millet

Millet, a language server for Standard ML

To use with nvim:

  1. Install a Rust toolchain: https://rustup.rs
  2. Clone the repo
  3. Run cargo build --release --bin lang-srv
  4. Move target/release/lang-srv to somewhere on your $PATH as millet

Snippet to enable the language server:

require'lspconfig'.millet.setup{}

Default config:

mint

https://www.mint-lang.com

Install Mint using the instructions. The language server is included since version 0.12.0.

Snippet to enable the language server:

require'lspconfig'.mint.setup{}

Default config:

mlir_lsp_server

https://mlir.llvm.org/docs/Tools/MLIRLSP/#mlir-lsp-language-server--mlir-lsp-server=

The Language Server for the LLVM MLIR language

mlir-lsp-server can be installed at the llvm-project repository (https://github.com/llvm/llvm-project)

Snippet to enable the language server:

require'lspconfig'.mlir_lsp_server.setup{}

Default config:

mlir_pdll_lsp_server

https://mlir.llvm.org/docs/Tools/MLIRLSP/#pdll-lsp-language-server--mlir-pdll-lsp-server

The Language Server for the LLVM PDLL language

mlir-pdll-lsp-server can be installed at the llvm-project repository (https://github.com/llvm/llvm-project)

Snippet to enable the language server:

require'lspconfig'.mlir_pdll_lsp_server.setup{}

Default config:

mm0_ls

https://github.com/digama0/mm0

Language Server for the metamath-zero theorem prover.

Requires mm0-rs to be installed and available on the PATH.

Snippet to enable the language server:

require'lspconfig'.mm0_ls.setup{}

Default config:

mojo

https://github.com/modularml/mojo

mojo-lsp-server can be installed via Modular

Mojo is a new programming language that bridges the gap between research and production by combining Python syntax and ecosystem with systems programming and metaprogramming features.

Snippet to enable the language server:

require'lspconfig'.mojo.setup{}

Default config:

motoko_lsp

https://github.com/dfinity/vscode-motoko

Language server for the Motoko programming language.

Snippet to enable the language server:

require'lspconfig'.motoko_lsp.setup{}

Default config:

move_analyzer

https://github.com/move-language/move/tree/main/language/move-analyzer

Language server for Move

The move-analyzer can be installed by running:

cargo install --git https://github.com/move-language/move move-analyzer

See move-analyzer's doc for details.

Snippet to enable the language server:

require'lspconfig'.move_analyzer.setup{}

Default config:

msbuild_project_tools_server

https://github.com/tintoy/msbuild-project-tools-server/

MSBuild Project Tools Server can be installed by following the README.MD on the above repository.

Example config:

lspconfig.msbuild_project_tools_server.setup {
  cmd = {'dotnet', '/path/to/server/MSBuildProjectTools.LanguageServer.Host.dll'}
}

There's no builtin filetypes for msbuild files, would require some filetype aliases:

vim.filetype.add({
  extension = {
    props = 'msbuild',
    tasks = 'msbuild',
    targets = 'msbuild',
  },
  pattern = {
    [ [[.*\..*proj]] ] = 'msbuild',
  },
})

Optionally tell treesitter to treat msbuild as xml so you can get syntax highlighting if you have the treesitter-xml-parser installed.

vim.treesitter.language.register('xml', { 'msbuild' })

Snippet to enable the language server:

require'lspconfig'.msbuild_project_tools_server.setup{}

Default config:

mutt_ls

https://github.com/neomutt/mutt-language-server

A language server for (neo)mutt's muttrc. It can be installed via pip.

pip install mutt-language-server

Snippet to enable the language server:

require'lspconfig'.mutt_ls.setup{}

Default config:

nelua_lsp

https://github.com/codehz/nelua-lsp

nelua-lsp is an experimental nelua language server.

You need nelua.vim for nelua files to be recognized or add this to your config:

in vimscript:

au BufNewFile,BufRead *.nelua setf nelua

in lua:

vim.api.nvim_create_autocmd({ "BufNewFile", "BufRead" }, { pattern = { "*.nelua" }, command = "setf nelua"})

By default, nelua-lsp doesn't have a cmd set. This is because nvim-lspconfig does not make assumptions about your path. You must add the following to your init.vim or init.lua to set cmd to the absolute path ($HOME and ~ are not expanded) of the unzipped run script or binary.

require'lspconfig'.nelua_lsp.setup {
    cmd = { "nelua", "-L", "/path/to/nelua-lsp/", "--script", "/path/to/nelua-lsp/nelua-lsp.lua" },
}

Snippet to enable the language server:

require'lspconfig'.nelua_lsp.setup{}

Default config:

neocmake

https://github.com/Decodetalkers/neocmakelsp

CMake LSP Implementation

Neovim does not currently include built-in snippets. neocmakelsp only provides completions when snippet support is enabled. To enable completion, install a snippet plugin and add the following override to your language client capabilities during setup.

--Enable (broadcasting) snippet capability for completion
local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities.textDocument.completion.completionItem.snippetSupport = true

require'lspconfig'.neocmake.setup {
  capabilities = capabilities,
}

Snippet to enable the language server:

require'lspconfig'.neocmake.setup{}

Default config:

nextflow_ls

https://github.com/nextflow-io/language-server

Requirements:

  • Java 17+

nextflow_ls can be installed by following the instructions here.

If you have installed nextflow language server, you can set the cmd custom path as follow:

require'lspconfig'.nextflow_ls.setup{
    cmd = { 'java', '-jar', 'nextflow-language-server-all.jar' },
    filetypes = { 'nextflow' },
    root_dir = util.root_pattern('nextflow.config', '.git'),
    settings = {
      nextflow = {
        files = {
          exclude = { '.git', '.nf-test', 'work' },
        },
      },
    },
}

Snippet to enable the language server:

require'lspconfig'.nextflow_ls.setup{}

Default config:

  • cmd : 
    { "java", "-jar", "nextflow-language-server-all.jar" }
  • filetypes : 
    { "nextflow" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/nextflow_ls.lua:4
  • settings : 
    {
  nextflow = {
    files = {
      exclude = { ".git", ".nf-test", "work" }
    }
  }
}

nextls

https://github.com/elixir-tools/next-ls

By default, next-ls does not set its cmd. Please see the following detailed instructions for possible installation methods.

Snippet to enable the language server:

require'lspconfig'.nextls.setup{}

Default config:

nginx_language_server

https://pypi.org/project/nginx-language-server/

nginx-language-server can be installed via pip:

pip install -U nginx-language-server

Snippet to enable the language server:

require'lspconfig'.nginx_language_server.setup{}

Default config:

nickel_ls

Nickel Language Server

https://github.com/tweag/nickel

nls can be installed with nix, or cargo, from the Nickel repository.

git clone https://github.com/tweag/nickel.git

Nix:

cd nickel
nix-env -f . -i

cargo:

cd nickel/lsp/nls
cargo install --path .

In order to have lspconfig detect Nickel filetypes (a prerequisite for autostarting a server), install the Nickel vim plugin.

Snippet to enable the language server:

require'lspconfig'.nickel_ls.setup{}

Default config:

nil_ls

https://github.com/oxalica/nil

A new language server for Nix Expression Language.

If you are using Nix with Flakes support, run nix profile install github:oxalica/nil to install. Check the repository README for more information.

See an example config at https://github.com/oxalica/nil/blob/main/dev/nvim-lsp.nix.

Snippet to enable the language server:

require'lspconfig'.nil_ls.setup{}

Default config:

nim_langserver

https://github.com/nim-lang/langserver

nim-langserver can be installed via the nimble package manager:

nimble install nimlangserver

Snippet to enable the language server:

require'lspconfig'.nim_langserver.setup{}

Default config:

nimls

https://github.com/PMunch/nimlsp

nimlsp can be installed via the nimble package manager:

nimble install nimlsp

Snippet to enable the language server:

require'lspconfig'.nimls.setup{}

Default config:

nixd

https://github.com/nix-community/nixd

Nix language server, based on nix libraries.

If you are using Nix with Flakes support, run nix profile install github:nix-community/nixd to install. Check the repository README for more information.

Snippet to enable the language server:

require'lspconfig'.nixd.setup{}

Default config:

nomad_lsp

https://github.com/juliosueiras/nomad-lsp

Written in Go, compilation is needed for nomad_lsp to be used. Please see the original repository.

Add the executable to your system or vim PATH and it will be set to go.

No configuration option is needed unless you choose not to add nomad-lsp executable to the PATH. You should know what you are doing if you choose so.

require('lspconfig').nomad_lsp.setup{ }

However, a hcl.nomad or nomad filetype should be defined.

Description of your jobs should be written in .nomad files for the LSP client to configure the server's root_dir configuration option.

Snippet to enable the language server:

require'lspconfig'.nomad_lsp.setup{}

Default config:

ntt

https://github.com/nokia/ntt Installation instructions can be found here. Can be configured by passing a "settings" object to ntt.setup{}:

require('lspconfig').ntt.setup{
    settings = {
      ntt = {
      }
    }
}

Snippet to enable the language server:

require'lspconfig'.ntt.setup{}

Default config:

nushell

https://github.com/nushell/nushell

Nushell built-in language server.

Snippet to enable the language server:

require'lspconfig'.nushell.setup{}

Default config:

nxls

https://github.com/nrwl/nx-console/tree/master/apps/nxls

nxls, a language server for Nx Workspaces

nxls can be installed via npm:

npm i -g nxls

Snippet to enable the language server:

require'lspconfig'.nxls.setup{}

Default config:

ocamlls

https://github.com/ocaml-lsp/ocaml-language-server

ocaml-language-server can be installed via npm

npm install -g ocaml-language-server

Snippet to enable the language server:

require'lspconfig'.ocamlls.setup{}

Default config:

ocamllsp

https://github.com/ocaml/ocaml-lsp

ocaml-lsp can be installed as described in installation guide.

To install the lsp server in a particular opam switch:

opam install ocaml-lsp-server

Snippet to enable the language server:

require'lspconfig'.ocamllsp.setup{}

Default config:

ols

https://github.com/DanielGavin/ols

       `Odin Language Server`.

Snippet to enable the language server:

require'lspconfig'.ols.setup{}

Default config:

omnisharp

https://github.com/omnisharp/omnisharp-roslyn OmniSharp server based on Roslyn workspaces

omnisharp-roslyn can be installed by downloading and extracting a release from here. OmniSharp can also be built from source by following the instructions here.

OmniSharp requires the dotnet-sdk to be installed.

By default, omnisharp-roslyn doesn't have a cmd set. This is because nvim-lspconfig does not make assumptions about your path. You must add the following to your init.vim or init.lua to set cmd to the absolute path ($HOME and ~ are not expanded) of the unzipped run script or binary.

For go_to_definition to work fully, extended textDocument/definition handler is needed, for example see omnisharp-extended-lsp.nvim

require'lspconfig'.omnisharp.setup {
    cmd = { "dotnet", "/path/to/omnisharp/OmniSharp.dll" },

    settings = {
      FormattingOptions = {
        -- Enables support for reading code style, naming convention and analyzer
        -- settings from .editorconfig.
        EnableEditorConfigSupport = true,
        -- Specifies whether 'using' directives should be grouped and sorted during
        -- document formatting.
        OrganizeImports = nil,
      },
      MsBuild = {
        -- If true, MSBuild project system will only load projects for files that
        -- were opened in the editor. This setting is useful for big C# codebases
        -- and allows for faster initialization of code navigation features only
        -- for projects that are relevant to code that is being edited. With this
        -- setting enabled OmniSharp may load fewer projects and may thus display
        -- incomplete reference lists for symbols.
        LoadProjectsOnDemand = nil,
      },
      RoslynExtensionsOptions = {
        -- Enables support for roslyn analyzers, code fixes and rulesets.
        EnableAnalyzersSupport = nil,
        -- Enables support for showing unimported types and unimported extension
        -- methods in completion lists. When committed, the appropriate using
        -- directive will be added at the top of the current file. This option can
        -- have a negative impact on initial completion responsiveness,
        -- particularly for the first few completion sessions after opening a
        -- solution.
        EnableImportCompletion = nil,
        -- Only run analyzers against open files when 'enableRoslynAnalyzers' is
        -- true
        AnalyzeOpenDocumentsOnly = nil,
      },
      Sdk = {
        -- Specifies whether to include preview versions of the .NET SDK when
        -- determining which version to use for project loading.
        IncludePrereleases = true,
      },
    },
}

Snippet to enable the language server:

require'lspconfig'.omnisharp.setup{}

Default config:

opencl_ls

https://github.com/Galarius/opencl-language-server

Build instructions can be found here.

Prebuilt binaries are available for Linux, macOS and Windows here.

Snippet to enable the language server:

require'lspconfig'.opencl_ls.setup{}

Default config:

openedge_ls

Language server for Progress OpenEdge ABL.

For manual installation, download abl-lsp.jar from the VSCode extension.

Configuration

require('lspconfig').['openedge_ls'].setup {
  oe_jar_path = '/path/to/abl-lsp.jar',
  dlc = '12.2:/path/to/dlc-12.2', -- Version number and OpenEdge root directory (colon separator)
  debug = false, -- Set to true for debug logging
  trace = false -- Set to true for trace logging (REALLY verbose)
}

Snippet to enable the language server:

require'lspconfig'.openedge_ls.setup{}

Default config:

openscad_ls

https://github.com/dzhu/openscad-language-server

A Language Server Protocol server for OpenSCAD

You can build and install openscad-language-server binary with cargo:

cargo install openscad-language-server

Vim does not have built-in syntax for the openscad filetype currently.

This can be added via an autocmd:

vim.cmd [[ autocmd BufRead,BufNewFile *.scad set filetype=openscad ]]

or by installing a filetype plugin such as https://github.com/sirtaj/vim-openscad

Snippet to enable the language server:

require'lspconfig'.openscad_ls.setup{}

Default config:

openscad_lsp

https://github.com/Leathong/openscad-LSP

A Language Server Protocol server for OpenSCAD

You can build and install openscad-lsp binary with cargo:

cargo install openscad-lsp

Snippet to enable the language server:

require'lspconfig'.openscad_lsp.setup{}

Default config:

oxlint

https://oxc.rs

A collection of JavaScript tools written in Rust.

npm install [-g] oxlint

Snippet to enable the language server:

require'lspconfig'.oxlint.setup{}

Default config:

  • cmd : 
    { "oxc_language_server" }
  • filetypes : 
    { "astro", "javascript", "javascriptreact", "svelte", "typescript", "typescript.tsx", "typescriptreact", "vue" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/oxlint.lua:4
  • single_file_support : false

pact_ls

https://github.com/kadena-io/pact-lsp

The Pact language server

Snippet to enable the language server:

require'lspconfig'.pact_ls.setup{}

Default config:

pasls

https://github.com/genericptr/pascal-language-server

An LSP server implementation for Pascal variants that are supported by Free Pascal, including Object Pascal. It uses CodeTools from Lazarus as backend.

First set cmd to the Pascal lsp binary.

Customization options are passed to pasls as environment variables for example in your .bashrc:

export FPCDIR='/usr/lib/fpc/src'      # FPC source directory (This is the only required option for the server to work).
export PP='/usr/lib/fpc/3.2.2/ppcx64' # Path to the Free Pascal compiler executable.
export LAZARUSDIR='/usr/lib/lazarus'  # Path to the Lazarus sources.
export FPCTARGET=''                   # Target operating system for cross compiling.
export FPCTARGETCPU='x86_64'          # Target CPU for cross compiling.

Snippet to enable the language server:

require'lspconfig'.pasls.setup{}

Default config:

pbls

https://git.sr.ht/~rrc/pbls

Prerequisites: Ensure protoc is on your $PATH.

pbls can be installed via cargo install:

cargo install --git https://git.sr.ht/~rrc/pbls

pbls is a Language Server for protobuf

Snippet to enable the language server:

require'lspconfig'.pbls.setup{}

Default config:

perlls

https://github.com/richterger/Perl-LanguageServer/tree/master/clients/vscode/perl

Perl-LanguageServer, a language server for Perl.

To use the language server, ensure that you have Perl::LanguageServer installed and perl command is on your path.

Snippet to enable the language server:

require'lspconfig'.perlls.setup{}

Default config:

  • cmd : 
    { "perl", "-MPerl::LanguageServer", "-e", "Perl::LanguageServer::run", "--", "--port 13603", "--nostdio 0" }
  • filetypes : 
    { "perl" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/perlls.lua:2
  • settings : 
    {
  perl = {
    fileFilter = { ".pm", ".pl" },
    ignoreDirs = ".git",
    perlCmd = "perl",
    perlInc = " "
  }
}
  • single_file_support : true

perlnavigator

https://github.com/bscan/PerlNavigator

A Perl language server. It can be installed via npm:

npm i -g perlnavigator-server

At minimum, you will need perl in your path. If you want to use a non-standard perl you will need to set your configuration like so:

settings = {
  perlnavigator = {
    perlPath = '/some/odd/location/my-perl'
  }
}

The contributes.configuration.properties section of perlnavigator's package.json has all available configuration settings. All settings have a reasonable default, but, at minimum, you may want to point perlnavigator at your perltidy and perlcritic configurations.

Snippet to enable the language server:

require'lspconfig'.perlnavigator.setup{}

Default config:

perlpls

https://github.com/FractalBoy/perl-language-server https://metacpan.org/pod/PLS

PLS, another language server for Perl.

To use the language server, ensure that you have PLS installed and that it is in your path

Snippet to enable the language server:

require'lspconfig'.perlpls.setup{}

Default config:

  • cmd : 
    { "pls" }
  • filetypes : 
    { "perl" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/perlpls.lua:2
  • settings : 
    {
  perl = {
    perlcritic = {
      enabled = false
    },
    syntax = {
      enabled = true
    }
  }
}
  • single_file_support : true

pest_ls

https://github.com/pest-parser/pest-ide-tools

Language server for pest grammars.

Snippet to enable the language server:

require'lspconfig'.pest_ls.setup{}

Default config:

phan

https://github.com/phan/phan

Installation: https://github.com/phan/phan#getting-started

Snippet to enable the language server:

require'lspconfig'.phan.setup{}

Default config:

  • cmd : 
    { "phan", "-m", "json", "--no-color", "--no-progress-bar", "-x", "-u", "-S", "--language-server-on-stdin", "--allow-polyfill-parser" }
  • filetypes : 
    { "php" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/phan.lua:17
  • single_file_support : true

phpactor

https://github.com/phpactor/phpactor

Installation: https://phpactor.readthedocs.io/en/master/usage/standalone.html#global-installation

Snippet to enable the language server:

require'lspconfig'.phpactor.setup{}

Default config:

pico8_ls

https://github.com/japhib/pico8-ls

Full language support for the PICO-8 dialect of Lua.

Snippet to enable the language server:

require'lspconfig'.pico8_ls.setup{}

Default config:

pkgbuild_language_server

https://github.com/Freed-Wu/pkgbuild-language-server

Language server for ArchLinux/Windows Msys2's PKGBUILD.

Snippet to enable the language server:

require'lspconfig'.pkgbuild_language_server.setup{}

Default config:

please

https://github.com/thought-machine/please

High-performance extensible build system for reproducible multi-language builds.

The plz binary will automatically install the LSP for you on first run

Snippet to enable the language server:

require'lspconfig'.please.setup{}

Default config:

poryscript_pls

https://github.com/huderlem/poryscript-pls

Language server for poryscript (a high level scripting language for GBA-era Pokémon decompilation projects)

Snippet to enable the language server:

require'lspconfig'.poryscript_pls.setup{}

Default config:

postgres_lsp

https://github.com/supabase/postgres_lsp

A Language Server for Postgres

Snippet to enable the language server:

require'lspconfig'.postgres_lsp.setup{}

Default config:

powershell_es

https://github.com/PowerShell/PowerShellEditorServices

Language server for PowerShell.

To install, download and extract PowerShellEditorServices.zip from the releases. To configure the language server, set the property bundle_path to the root of the extracted PowerShellEditorServices.zip.

The default configuration doesn't set cmd unless bundle_path is specified.

require'lspconfig'.powershell_es.setup{
  bundle_path = 'c:/w/PowerShellEditorServices',
}

By default the languageserver is started in pwsh (PowerShell Core). This can be changed by specifying shell.

require'lspconfig'.powershell_es.setup{
  bundle_path = 'c:/w/PowerShellEditorServices',
  shell = 'powershell.exe',
}

Note that the execution policy needs to be set to Unrestricted for the languageserver run under PowerShell

If necessary, specific cmd can be defined instead of bundle_path. See PowerShellEditorServices to learn more.

require'lspconfig'.powershell_es.setup{
  cmd = {'pwsh', '-NoLogo', '-NoProfile', '-Command', "c:/PSES/Start-EditorServices.ps1 ..."}
}

Snippet to enable the language server:

require'lspconfig'.powershell_es.setup{}

Default config:

prismals

Language Server for the Prisma JavaScript and TypeScript ORM

@prisma/language-server can be installed via npm

npm install -g @prisma/language-server

Snippet to enable the language server:

require'lspconfig'.prismals.setup{}

Default config:

  • cmd : 
    { "prisma-language-server", "--stdio" }
  • filetypes : 
    { "prisma" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/prismals.lua:4
  • settings : 
    {
  prisma = {
    prismaFmtBinPath = ""
  }
}

prolog_ls

https://github.com/jamesnvc/lsp_server

Language Server Protocol server for SWI-Prolog

Snippet to enable the language server:

require'lspconfig'.prolog_ls.setup{}

Default config:

  • cmd : 
    { "swipl", "-g", "use_module(library(lsp_server)).", "-g", "lsp_server:main", "-t", "halt", "--", "stdio" }
  • filetypes : 
    { "prolog" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/prolog_ls.lua:4
  • single_file_support : true

prosemd_lsp

https://github.com/kitten/prosemd-lsp

An experimental LSP for Markdown.

Please see the manual installation instructions: https://github.com/kitten/prosemd-lsp#manual-installation

Snippet to enable the language server:

require'lspconfig'.prosemd_lsp.setup{}

Default config:

protols

https://github.com/coder3101/protols

protols can be installed via cargo:

cargo install protols

A Language Server for proto3 files. It uses tree-sitter and runs in single file mode.

Snippet to enable the language server:

require'lspconfig'.protols.setup{}

Default config:

psalm

https://github.com/vimeo/psalm

Can be installed with composer.

composer global require vimeo/psalm

Snippet to enable the language server:

require'lspconfig'.psalm.setup{}

Default config:

pug

https://github.com/opa-oz/pug-lsp

An implementation of the Language Protocol Server for Pug.js

PugLSP can be installed via go get github.com/opa-oz/pug-lsp, or manually downloaded from releases page

Snippet to enable the language server:

require'lspconfig'.pug.setup{}

Default config:

puppet

LSP server for Puppet.

Installation:

  • Clone the editor-services repository: https://github.com/puppetlabs/puppet-editor-services

  • Navigate into that directory and run: bundle install

  • Install the 'puppet-lint' gem: gem install puppet-lint

  • Add that repository to $PATH.

  • Ensure you can run puppet-languageserver from outside the editor-services directory.

Snippet to enable the language server:

require'lspconfig'.puppet.setup{}

Default config:

purescriptls

https://github.com/nwolverson/purescript-language-server

The purescript-language-server can be added to your project and $PATH via

  • JavaScript package manager such as npm, pnpm, Yarn, et al.
  • Nix under the nodePackages and nodePackages_latest package sets

Snippet to enable the language server:

require'lspconfig'.purescriptls.setup{}

Default config:

pylsp

https://github.com/python-lsp/python-lsp-server

A Python 3.6+ implementation of the Language Server Protocol.

See the project's README for installation instructions.

Configuration options are documented here. In order to configure an option, it must be translated to a nested Lua table and included in the settings argument to the setup{} function. For example, in order to set the pylsp.plugins.pycodestyle.ignore option:

require'lspconfig'.pylsp.setup{
  settings = {
    pylsp = {
      plugins = {
        pycodestyle = {
          ignore = {'W391'},
          maxLineLength = 100
        }
      }
    }
  }
}

Note: This is a community fork of pyls.

Snippet to enable the language server:

require'lspconfig'.pylsp.setup{}

Default config:

pylyzer

https://github.com/mtshiba/pylyzer

pylyzer, a fast static code analyzer & language server for Python.

Snippet to enable the language server:

require'lspconfig'.pylyzer.setup{}

Default config:

  • cmd : 
    { "pylyzer", "--server" }
  • filetypes : 
    { "python" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/pylyzer.lua:4
  • settings : 
    {
  python = {
    checkOnType = false,
    diagnostics = true,
    inlayHints = true,
    smartCompletion = true
  }
}
  • single_file_support : true

pyre

https://pyre-check.org/

pyre a static type checker for Python 3.

pyre offers an extremely limited featureset. It currently only supports diagnostics, which are triggered on save.

Do not report issues for missing features in pyre to lspconfig.

Snippet to enable the language server:

require'lspconfig'.pyre.setup{}

Default config:

pyright

https://github.com/microsoft/pyright

pyright, a static type checker and language server for python

Snippet to enable the language server:

require'lspconfig'.pyright.setup{}

Commands:

  • PyrightOrganizeImports: Organize Imports
  • PyrightSetPythonPath: Reconfigure pyright with the provided python path

Default config:

  • cmd : 
    { "pyright-langserver", "--stdio" }
  • filetypes : 
    { "python" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/pyright.lua:44
  • settings : 
    {
  python = {
    analysis = {
      autoSearchPaths = true,
      diagnosticMode = "openFilesOnly",
      useLibraryCodeForTypes = true
    }
  }
}
  • single_file_support : true

qml_lsp

https://invent.kde.org/sdk/qml-lsp

LSP implementation for QML (autocompletion, live linting, etc. in editors)

Snippet to enable the language server:

require'lspconfig'.qml_lsp.setup{}

Default config:

qmlls

https://github.com/qt/qtdeclarative

LSP implementation for QML (autocompletion, live linting, etc. in editors),

Snippet to enable the language server:

require'lspconfig'.qmlls.setup{}

Default config:

quick_lint_js

https://quick-lint-js.com/

quick-lint-js finds bugs in JavaScript programs.

See installation instructions

Snippet to enable the language server:

require'lspconfig'.quick_lint_js.setup{}

Default config:

r_language_server

languageserver is an implementation of the Microsoft's Language Server Protocol for the R language.

It is released on CRAN and can be easily installed by

install.packages("languageserver")

Snippet to enable the language server:

require'lspconfig'.r_language_server.setup{}

Default config:

racket_langserver

https://github.com/jeapostrophe/racket-langserver

The Racket language server. This project seeks to use DrRacket's public API to provide functionality that mimics DrRacket's code tools as closely as possible.

Install via raco: raco pkg install racket-langserver

Snippet to enable the language server:

require'lspconfig'.racket_langserver.setup{}

Default config:

raku_navigator

https://github.com/bscan/RakuNavigator A Raku language server By default, raku_navigator doesn't have a cmd set. This is because nvim-lspconfig does not make assumptions about your path. You have to install the language server manually. Clone the RakuNavigator repo, install based on the instructions, and point cmd to server.js inside the server/out directory:

cmd = {'node', '<path_to_repo>/server/out/server.js', '--stdio'}

At minimum, you will need raku in your path. If you want to use a non-standard raku you will need to set your configuration like so:

settings = {
  raku_navigator = {
    rakuPath = '/some/odd/location/my-raku'
  }
}

The contributes.configuration.properties section of raku_navigator's package.json has all available configuration settings. All settings have a reasonable default, but, at minimum, you may want to point raku_navigator at your raku_tidy and raku_critic configurations.

Snippet to enable the language server:

require'lspconfig'.raku_navigator.setup{}

Default config:

reason_ls

Reason language server

You can install reason language server from reason-language-server repository.

Snippet to enable the language server:

require'lspconfig'.reason_ls.setup{}

Default config:

regal

https://github.com/StyraInc/regal

A linter for Rego, with support for running as an LSP server.

regal can be installed by running:

go install github.com/StyraInc/regal@latest

Snippet to enable the language server:

require'lspconfig'.regal.setup{}

Default config:

regols

https://github.com/kitagry/regols

OPA Rego language server.

regols can be installed by running:

go install github.com/kitagry/regols@latest

Snippet to enable the language server:

require'lspconfig'.regols.setup{}

Default config:

relay_lsp

https://github.com/facebook/relay Relay is a JavaScript framework for building data-driven React applications

Setup:

- Make sure you have a Relay config file somewhere in your project.
- We support standard config file formats (`.yml`, `.js`, `.json`), and the the `relay` field in your `package.json`
- Make sure you have the `relay-compiler` installed in your project. The bare minimum is v13.
- Make sure you are able to run the `relay-compiler` command from the command line. If `yarn relay-compiler` works, it's very likely that the LSP will work.
- Remove / disable any conflicting GraphQL LSPs you have installed.

Relay LSP is a part of the Relay Compiler binary and available when adding `relay-compiler` to your project's devDependencies.

```lua
require'lspconfig'.relay_lsp.setup {
  -- (default: false) Whether or not we should automatically start
  -- the Relay Compiler in watch mode when you open a project
  auto_start_compiler = false,


  -- (default: null) Path to a relay config relative to the
  -- `root_dir`. Without this, the compiler will search for your
  -- config. This is helpful if your relay project is in a nested
  -- directory.
  path_to_config = nil,
}
```

Snippet to enable the language server:

require'lspconfig'.relay_lsp.setup{}

Default config:

remark_ls

https://github.com/remarkjs/remark-language-server

remark-language-server can be installed via npm:

npm install -g remark-language-server

remark-language-server uses the same configuration files as remark-cli.

This uses a plugin based system. Each plugin needs to be installed locally using npm or yarn.

For example, given the following .remarkrc.json:

{
  "presets": [
    "remark-preset-lint-recommended"
  ]
}

remark-preset-lint-recommended needs to be installed in the local project:

npm install remark-preset-lint-recommended

Snippet to enable the language server:

require'lspconfig'.remark_ls.setup{}

Default config:

rescriptls

https://github.com/rescript-lang/rescript-vscode/tree/master/server

ReScript Language Server can be installed via npm:

npm install -g @rescript/language-server

See package.json for init_options supported.

For example, in order to disable the inlayHints option:

require'lspconfig'.pylsp.setup{
  settings = {
    rescript = {
      settings = {
        inlayHints = { enable = false },
      },
    },
  }
}

Snippet to enable the language server:

require'lspconfig'.rescriptls.setup{}

Default config:

  • cmd : 
    { "rescript-language-server", "--stdio" }
  • filetypes : 
    { "rescript" }
  • init_options : 
    {
  extensionConfiguration = {
    allowBuiltInFormatter = true,
    askToStartBuild = false,
    cache = {
      projectConfig = {
        enabled = true
      }
    },
    codeLens = true,
    incrementalTypechecking = {
      acrossFiles = true,
      enabled = true
    },
    inlayHints = {
      enable = true
    }
  }
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/rescriptls.lua:4
  • settings : 
    {}

rls

https://github.com/rust-lang/rls

rls, a language server for Rust

See https://github.com/rust-lang/rls#setup to setup rls itself. See https://github.com/rust-lang/rls#configuration for rls-specific settings. All settings listed on the rls configuration section of the readme must be set under settings.rust as follows:

nvim_lsp.rls.setup {
  settings = {
    rust = {
      unstable_features = true,
      build_on_save = false,
      all_features = true,
    },
  },
}

If you want to use rls for a particular build, eg nightly, set cmd as follows:

cmd = {"rustup", "run", "nightly", "rls"}

Snippet to enable the language server:

require'lspconfig'.rls.setup{}

Default config:

rnix

https://github.com/nix-community/rnix-lsp

A language server for Nix providing basic completion and formatting via nixpkgs-fmt.

To install manually, run cargo install rnix-lsp. If you are using nix, rnix-lsp is in nixpkgs.

This server accepts configuration via the settings key.

Snippet to enable the language server:

require'lspconfig'.rnix.setup{}

Default config:

robotcode

https://robotcode.io

RobotCode - Language Server Protocol implementation for Robot Framework.

Snippet to enable the language server:

require'lspconfig'.robotcode.setup{}

Default config:

robotframework_ls

https://github.com/robocorp/robotframework-lsp

Language Server Protocol implementation for Robot Framework.

Snippet to enable the language server:

require'lspconfig'.robotframework_ls.setup{}

Default config:

roc_ls

https://github.com/roc-lang/roc/tree/main/crates/language_server#roc_language_server

The built-in language server for the Roc programming language. Installation

Snippet to enable the language server:

require'lspconfig'.roc_ls.setup{}

Default config:

rome

https://rome.tools

Language server for the Rome Frontend Toolchain.

(Unmaintained, use Biome instead.)

npm install [-g] rome

Snippet to enable the language server:

require'lspconfig'.rome.setup{}

Default config:

  • cmd : 
    { "rome", "lsp-proxy" }
  • filetypes : 
    { "javascript", "javascriptreact", "json", "typescript", "typescript.tsx", "typescriptreact" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/rome.lua:2
  • single_file_support : true

rubocop

https://github.com/rubocop/rubocop

Snippet to enable the language server:

require'lspconfig'.rubocop.setup{}

Default config:

ruby_lsp

https://shopify.github.io/ruby-lsp/

This gem is an implementation of the language server protocol specification for Ruby, used to improve editor features.

Install the gem. There's no need to require it, since the server is used as a standalone executable.

gem install ruby-lsp

Snippet to enable the language server:

require'lspconfig'.ruby_lsp.setup{}

Default config:

  • cmd : 
    { "ruby-lsp" }
  • filetypes : 
    { "ruby", "eruby" }
  • init_options : 
    {
  formatter = "auto"
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/ruby_lsp.lua:4
  • single_file_support : true

ruff

https://github.com/astral-sh/ruff

A Language Server Protocol implementation for Ruff, an extremely fast Python linter and code formatter, written in Rust. It can be installed via pip.

pip install ruff

Available in Ruff v0.4.5 in beta and stabilized in Ruff v0.5.3.

This is the new built-in language server written in Rust. It supports the same feature set as ruff-lsp, but with superior performance and no installation required. Note that the ruff-lsp server will continue to be maintained until further notice.

Server settings can be provided via:

require('lspconfig').ruff.setup({
  init_options = {
    settings = {
      -- Server settings should go here
    }
  }
})

Refer to the documentation for more details.

Snippet to enable the language server:

require'lspconfig'.ruff.setup{}

Default config:

ruff_lsp

https://github.com/astral-sh/ruff-lsp

A Language Server Protocol implementation for Ruff, an extremely fast Python linter and code transformation tool, written in Rust. It can be installed via pip.

pip install ruff-lsp

Extra CLI arguments for ruff can be provided via

require'lspconfig'.ruff_lsp.setup{
  init_options = {
    settings = {
      -- Any extra CLI arguments for `ruff` go here.
      args = {},
    }
  }
}

Snippet to enable the language server:

require'lspconfig'.ruff_lsp.setup{}

Default config:

rune_languageserver

https://crates.io/crates/rune-languageserver

A language server for the Rune Language, an embeddable dynamic programming language for Rust

Snippet to enable the language server:

require'lspconfig'.rune_languageserver.setup{}

Default config:

rust_analyzer

https://github.com/rust-lang/rust-analyzer

rust-analyzer (aka rls 2.0), a language server for Rust

See docs for extra settings. The settings can be used like this:

require'lspconfig'.rust_analyzer.setup{
  settings = {
    ['rust-analyzer'] = {
      diagnostics = {
        enable = false;
      }
    }
  }
}

Note: do not set init_options for this LS config, it will be automatically populated by the contents of settings["rust-analyzer"] per eb5da56d83/docs/dev/lsp-extensions.md (L26).

Snippet to enable the language server:

require'lspconfig'.rust_analyzer.setup{}

Commands:

  • CargoReload: Reload current cargo workspace

Default config:

salt_ls

Language server for Salt configuration files. https://github.com/dcermak/salt-lsp

The language server can be installed with pip:

pip install salt-lsp

Snippet to enable the language server:

require'lspconfig'.salt_ls.setup{}

Default config:

scheme_langserver

https://github.com/ufo5260987423/scheme-langserver scheme-langserver, a language server protocol implementation for scheme. And for nvim user, please add .sls to scheme file extension list.

Snippet to enable the language server:

require'lspconfig'.scheme_langserver.setup{}

Default config:

scry

https://github.com/crystal-lang-tools/scry

Crystal language server.

Snippet to enable the language server:

require'lspconfig'.scry.setup{}

Default config:

selene3p_ls

https://github.com/antonk52/lua-3p-language-servers

3rd party Language Server for Selene lua linter

Snippet to enable the language server:

require'lspconfig'.selene3p_ls.setup{}

Default config:

serve_d

https://github.com/Pure-D/serve-d

       `Microsoft language server protocol implementation for D using workspace-d.`
       Download a binary from https://github.com/Pure-D/serve-d/releases and put it in your $PATH.

Snippet to enable the language server:

require'lspconfig'.serve_d.setup{}

Default config:

shopify_theme_ls

https://shopify.dev/docs/api/shopify-cli

Language Server and Theme Check (linter) for Shopify themes.

shopify can be installed via npm npm install -g @shopify/cli.

Note: This LSP already includes Theme Check so you don't need to use the theme_check server configuration as well.

Snippet to enable the language server:

require'lspconfig'.shopify_theme_ls.setup{}

Default config:

sixtyfps

https://github.com/sixtyfpsui/sixtyfps SixtyFPS's language server

You can build and install sixtyfps-lsp binary with cargo:

cargo install sixtyfps-lsp

Vim does not have built-in syntax for the sixtyfps filetype currently.

This can be added via an autocmd:

vim.cmd [[ autocmd BufRead,BufNewFile *.60 set filetype=sixtyfps ]]

or by installing a filetype plugin such as https://github.com/RustemB/sixtyfps-vim

Snippet to enable the language server:

require'lspconfig'.sixtyfps.setup{}

Default config:

  • cmd : 
    { "sixtyfps-lsp" }
  • filetypes : 
    { "sixtyfps" }
  • single_file_support : true

slangd

https://github.com/shader-slang/slang

The slangd binary can be downloaded as part of slang releases or by building slang from source.

The server can be configured by passing a "settings" object to slangd.setup{}:

require('lspconfig').slangd.setup{
  settings = {
    slang = {
      predefinedMacros = {"MY_VALUE_MACRO=1"},
      inlayHints = {
        deducedTypes = true,
        parameterNames = true,
      }
    }
  }
}

Available options are documented here or in more detail here.

Snippet to enable the language server:

require'lspconfig'.slangd.setup{}

Default config:

slint_lsp

https://github.com/slint-ui/slint Slint's language server

You can build and install slint-lsp binary with cargo:

cargo install slint-lsp

Vim does not have built-in syntax for the slint filetype at this time.

This can be added via an autocmd:

vim.cmd [[ autocmd BufRead,BufNewFile *.slint set filetype=slint ]]

Snippet to enable the language server:

require'lspconfig'.slint_lsp.setup{}

Default config:

smarty_ls

https://github.com/landeaux/vscode-smarty-langserver-extracted

Language server for Smarty.

smarty-language-server can be installed via npm:

npm i -g vscode-smarty-langserver-extracted

Snippet to enable the language server:

require'lspconfig'.smarty_ls.setup{}

Default config:

  • cmd : 
    { "smarty-language-server", "--stdio" }
  • filetypes : 
    { "smarty" }
  • init_options : 
    {}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/smarty_ls.lua:4
  • settings : 
    {
  css = {
    validate = true
  },
  smarty = {
    pluginDirs = {}
  }
}

smithy_ls

https://github.com/awslabs/smithy-language-server

Smithy Language Server, A Language Server Protocol implementation for the Smithy IDL

Snippet to enable the language server:

require'lspconfig'.smithy_ls.setup{}

Default config:

snakeskin_ls

https://www.npmjs.com/package/@snakeskin/cli

snakeskin cli can be installed via npm:

npm install -g @snakeskin/cli

Snippet to enable the language server:

require'lspconfig'.snakeskin_ls.setup{}

Default config:

snyk_ls

https://github.com/snyk/snyk-ls

LSP for Snyk Open Source, Snyk Infrastructure as Code, and Snyk Code.

Snippet to enable the language server:

require'lspconfig'.snyk_ls.setup{}

Default config:

  • cmd : 
    { "snyk-ls" }
  • filetypes : 
    { "go", "gomod", "javascript", "typescript", "json", "python", "requirements", "helm", "yaml", "terraform", "terraform-vars" }
  • init_options : 
    {
  activateSnykCode = "true"
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/snyk_ls.lua:4
  • settings : 
    {}
  • single_file_support : true

solang

A language server for Solidity

See the documentation for installation instructions.

The language server only provides the following capabilities:

  • Syntax highlighting
  • Diagnostics
  • Hover

There is currently no support for completion, goto definition, references, or other functionality.

Snippet to enable the language server:

require'lspconfig'.solang.setup{}

Default config:

solargraph

https://solargraph.org/

solargraph, a language server for Ruby

You can install solargraph via gem install.

gem install --user-install solargraph

Snippet to enable the language server:

require'lspconfig'.solargraph.setup{}

Default config:

  • cmd : 
    { "solargraph", "stdio" }
  • filetypes : 
    { "ruby" }
  • init_options : 
    {
  formatting = true
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/solargraph.lua:4
  • settings : 
    {
  solargraph = {
    diagnostics = true
  }
}

solc

https://docs.soliditylang.org/en/latest/installing-solidity.html

solc is the native language server for the Solidity language.

Snippet to enable the language server:

require'lspconfig'.solc.setup{}

Default config:

solidity

https://github.com/qiuxiang/solidity-ls

npm i solidity-ls -g

Make sure that solc is installed and it's the same version of the file. solc-select is recommended.

Solidity language server is a LSP with autocomplete, go to definition and diagnostics.

If you use brownie, use this root_dir: root_dir = util.root_pattern('brownie-config.yaml', '.git')

on includePath, you can add an extra path to search for external libs, on remapping you can remap lib <> path, like:

{ solidity = { includePath = '/Users/your_user/.brownie/packages/', remapping = { ["@OpenZeppelin/"] = 'OpenZeppelin/openzeppelin-contracts@4.6.0/' } } }

For brownie users Change the root_dir to:

root_pattern("brownie-config.yaml", ".git")

The best way of using it is to have a package.json in your project folder with the packages that you will use. After installing with package.json, just create a remappings.txt with:

@OpenZeppelin/=node_modules/OpenZeppelin/openzeppelin-contracts@4.6.0/

You can omit the node_modules as well.

Snippet to enable the language server:

require'lspconfig'.solidity.setup{}

Default config:

  • cmd : 
    { "solidity-ls", "--stdio" }
  • filetypes : 
    { "solidity" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/solidity.lua:4
  • settings : 
    {
  solidity = {
    includePath = "",
    remapping = {}
  }
}

solidity_ls

https://github.com/juanfranblanco/vscode-solidity

vscode-solidity-server can be installed via npm:

npm install -g vscode-solidity-server

vscode-solidity-server is a language server for the Solidity language ported from the VSCode "solidity" extension.

Snippet to enable the language server:

require'lspconfig'.solidity_ls.setup{}

Default config:

solidity_ls_nomicfoundation

https://github.com/NomicFoundation/hardhat-vscode/blob/development/server/README.md

nomicfoundation-solidity-language-server can be installed via npm:

npm install -g @nomicfoundation/solidity-language-server

A language server for the Solidity programming language, built by the Nomic Foundation for the Ethereum community.

Snippet to enable the language server:

require'lspconfig'.solidity_ls_nomicfoundation.setup{}

Default config:

somesass_ls

https://github.com/wkillerud/some-sass/tree/main/packages/language-server

some-sass-language-server can be installed via npm:

npm i -g some-sass-language-server

The language server provides:

  • Full support for @use and @forward, including aliases, prefixes and hiding.
  • Workspace-wide code navigation and refactoring, such as Rename Symbol.
  • Rich documentation through SassDoc.
  • Language features for %placeholder-selectors, both when using them and writing them.
  • Suggestions and hover info for built-in Sass modules, when used with @use.

Snippet to enable the language server:

require'lspconfig'.somesass_ls.setup{}

Default config:

  • cmd : 
    { "some-sass-language-server", "--stdio" }
  • filetypes : 
    { "scss", "sass" }
  • name : 
    "somesass_ls"
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/somesass_ls.lua:4
  • settings : 
    {
  somesass = {
    suggestAllFromOpenDocument = true
  }
}
  • single_file_support : true

sorbet

https://sorbet.org

Sorbet is a fast, powerful type checker designed for Ruby.

You can install Sorbet via gem install. You might also be interested in how to set Sorbet up for new projects: https://sorbet.org/docs/adopting.

gem install sorbet

Snippet to enable the language server:

require'lspconfig'.sorbet.setup{}

Default config:

sourcekit

https://github.com/apple/sourcekit-lsp

Language server for Swift and C/C++/Objective-C.

Snippet to enable the language server:

require'lspconfig'.sourcekit.setup{}

Default config:

sourcery

https://github.com/sourcery-ai/sourcery

Refactor Python instantly using the power of AI.

It requires the init_options param to be populated as shown below and will respond with the list of ServerCapabilities that it supports:

require'lspconfig'.sourcery.setup {
    init_options = {
        --- The Sourcery token for authenticating the user.
        --- This is retrieved from the Sourcery website and must be
        --- provided by each user. The extension must provide a
        --- configuration option for the user to provide this value.
        token = <YOUR_TOKEN>,

        --- The extension's name and version as defined by the extension.
        extension_version = 'vim.lsp',

        --- The editor's name and version as defined by the editor.
        editor_version = 'vim',
    },
}

Alternatively, you can login to sourcery by running sourcery login with sourcery-cli.

Snippet to enable the language server:

require'lspconfig'.sourcery.setup{}

Default config:

  • cmd : 
    { "sourcery", "lsp" }
  • filetypes : 
    { "javascript", "javascriptreact", "python", "typescript", "typescriptreact" }
  • init_options : 
    {
  editor_version = "vim",
  extension_version = "vim.lsp"
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/sourcery.lua:32
  • single_file_support : true

spectral

https://github.com/luizcorreia/spectral-language-server A flexible JSON/YAML linter for creating automated style guides, with baked in support for OpenAPI v2 & v3.

spectral-language-server can be installed via npm:

npm i -g spectral-language-server

See vscode-spectral for configuration options.

Snippet to enable the language server:

require'lspconfig'.spectral.setup{}

Default config:

  • cmd : 
    { "spectral-language-server", "--stdio" }
  • filetypes : 
    { "yaml", "json", "yml" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/spectral.lua:6
  • settings : 
    {
  enable = true,
  run = "onType",
  validateLanguages = { "yaml", "json", "yml" }
}
  • single_file_support : true

spyglassmc_language_server

https://github.com/SpyglassMC/Spyglass/tree/main/packages/language-server

Language server for Minecraft datapacks.

spyglassmc-language-server can be installed via npm:

npm i -g @spyglassmc/language-server

You may also need to configure the filetype:

autocmd BufNewFile,BufRead *.mcfunction set filetype=mcfunction

This is automatically done by CrystalAlpha358/vim-mcfunction, which also provide syntax highlight.

Snippet to enable the language server:

require'lspconfig'.spyglassmc_language_server.setup{}

Default config:

sqlls

https://github.com/joe-re/sql-language-server

This LSP can be installed via npm. Find further instructions on manual installation of the sql-language-server at joe-re/sql-language-server.

Snippet to enable the language server:

require'lspconfig'.sqlls.setup{}

Default config:

sqls

https://github.com/sqls-server/sqls

require'lspconfig'.sqls.setup{
  cmd = {"path/to/command", "-config", "path/to/config.yml"};
  ...
}

Sqls can be installed via go get github.com/sqls-server/sqls. Instructions for compiling Sqls from the source can be found at sqls-server/sqls.

Snippet to enable the language server:

require'lspconfig'.sqls.setup{}

Default config:

standardrb

https://github.com/testdouble/standard

Ruby Style Guide, with linter & automatic code fixer.

Snippet to enable the language server:

require'lspconfig'.standardrb.setup{}

Default config:

starlark_rust

https://github.com/facebookexperimental/starlark-rust/ The LSP part of starlark-rust is not currently documented, but the implementation works well for linting. This gives valuable warnings for potential issues in the code, but does not support refactorings.

It can be installed with cargo: https://crates.io/crates/starlark

Snippet to enable the language server:

require'lspconfig'.starlark_rust.setup{}

Default config:

starpls

https://github.com/withered-magic/starpls

starpls is an LSP implementation for Starlark. Installation instructions can be found in the project's README.

Snippet to enable the language server:

require'lspconfig'.starpls.setup{}

Default config:

statix

https://github.com/nerdypepper/statix

lints and suggestions for the nix programming language

Snippet to enable the language server:

require'lspconfig'.statix.setup{}

Default config:

steep

https://github.com/soutaro/steep

steep is a static type checker for Ruby.

You need Steepfile to make it work. Generate it with steep init.

Snippet to enable the language server:

require'lspconfig'.steep.setup{}

Default config:

stimulus_ls

https://www.npmjs.com/package/stimulus-language-server

stimulus-lsp can be installed via npm:

npm install -g stimulus-language-server

or via yarn:

yarn global add stimulus-language-server

Snippet to enable the language server:

require'lspconfig'.stimulus_ls.setup{}

Default config:

stylelint_lsp

https://github.com/bmatcuk/stylelint-lsp

stylelint-lsp can be installed via npm:

npm i -g stylelint-lsp

Can be configured by passing a settings.stylelintplus object to stylelint_lsp.setup:

require'lspconfig'.stylelint_lsp.setup{
  settings = {
    stylelintplus = {
      -- see available options in stylelint-lsp documentation
    }
  }
}

Snippet to enable the language server:

require'lspconfig'.stylelint_lsp.setup{}

Default config:

stylua3p_ls

https://github.com/antonk52/lua-3p-language-servers

3rd party Language Server for Stylua lua formatter

Snippet to enable the language server:

require'lspconfig'.stylua3p_ls.setup{}

Default config:

superhtml

https://github.com/kristoff-it/superhtml

HTML Language Server & Templating Language Library

This LSP is designed to tightly adhere to the HTML spec as well as enforcing some additional rules that ensure HTML clarity.

If you want to disable HTML support for another HTML LSP, add the following to your configuration:

require'lspconfig'.superhtml.setup {
  filetypes = { 'superhtml' }
}

Snippet to enable the language server:

require'lspconfig'.superhtml.setup{}

Default config:

svelte

https://github.com/sveltejs/language-tools/tree/master/packages/language-server

Note: assuming that ts_ls is setup, full JavaScript/TypeScript support (find references, rename, etc of symbols in Svelte files when working in JS/TS files) requires per-project installation and configuration of typescript-svelte-plugin.

svelte-language-server can be installed via npm:

npm install -g svelte-language-server

Snippet to enable the language server:

require'lspconfig'.svelte.setup{}

Default config:

svlangserver

https://github.com/imc-trading/svlangserver

Language server for SystemVerilog.

svlangserver can be installed via npm:

$ npm install -g @imc-trading/svlangserver

Snippet to enable the language server:

require'lspconfig'.svlangserver.setup{}

Commands:

  • SvlangserverBuildIndex: Instructs language server to rerun indexing
  • SvlangserverReportHierarchy: Generates hierarchy for the given module

Default config:

  • cmd : 
    { "svlangserver" }
  • filetypes : 
    { "verilog", "systemverilog" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/svlangserver.lua:19
  • settings : 
    {
  systemverilog = {
    includeIndexing = { "*.{v,vh,sv,svh}", "**/*.{v,vh,sv,svh}" }
  }
}
  • single_file_support : true

svls

https://github.com/dalance/svls

Language server for verilog and SystemVerilog

svls can be installed via cargo:

cargo install svls

Snippet to enable the language server:

require'lspconfig'.svls.setup{}

Default config:

swift_mesonls

https://github.com/JCWasmx86/Swift-MesonLSP

Meson language server written in Swift

Snippet to enable the language server:

require'lspconfig'.swift_mesonls.setup{}

Default config:

syntax_tree

https://ruby-syntax-tree.github.io/syntax_tree/

A fast Ruby parser and formatter.

Syntax Tree is a suite of tools built on top of the internal CRuby parser. It provides the ability to generate a syntax tree from source, as well as the tools necessary to inspect and manipulate that syntax tree. It can be used to build formatters, linters, language servers, and more.

gem install syntax_tree

Snippet to enable the language server:

require'lspconfig'.syntax_tree.setup{}

Default config:

tabby_ml

https://tabby.tabbyml.com/blog/running-tabby-as-a-language-server

Language server for Tabby, an opensource, self-hosted AI coding assistant.

tabby-agent can be installed via npm:

npm install --global tabby-agent

Snippet to enable the language server:

require'lspconfig'.tabby_ml.setup{}

Default config:

tailwindcss

https://github.com/tailwindlabs/tailwindcss-intellisense

Tailwind CSS Language Server can be installed via npm:

npm install -g @tailwindcss/language-server

Snippet to enable the language server:

require'lspconfig'.tailwindcss.setup{}

Default config:

  • cmd : 
    { "tailwindcss-language-server", "--stdio" }
  • filetypes : 
    { "aspnetcorerazor", "astro", "astro-markdown", "blade", "clojure", "django-html", "htmldjango", "edge", "eelixir", "elixir", "ejs", "erb", "eruby", "gohtml", "gohtmltmpl", "haml", "handlebars", "hbs", "html", "htmlangular", "html-eex", "heex", "jade", "leaf", "liquid", "markdown", "mdx", "mustache", "njk", "nunjucks", "php", "razor", "slim", "twig", "css", "less", "postcss", "sass", "scss", "stylus", "sugarss", "javascript", "javascriptreact", "reason", "rescript", "typescript", "typescriptreact", "vue", "svelte", "templ" }
  • on_new_config source (use "gF" to visit): ../lua/lspconfig/configs/tailwindcss.lua:4
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/tailwindcss.lua:4
  • settings : 
    {
  tailwindCSS = {
    classAttributes = { "class", "className", "class:list", "classList", "ngClass" },
    includeLanguages = {
      eelixir = "html-eex",
      eruby = "erb",
      htmlangular = "html",
      templ = "html"
    },
    lint = {
      cssConflict = "warning",
      invalidApply = "error",
      invalidConfigPath = "error",
      invalidScreen = "error",
      invalidTailwindDirective = "error",
      invalidVariant = "error",
      recommendedVariantOrder = "warning"
    },
    validate = true
  }
}

taplo

https://taplo.tamasfe.dev/cli/usage/language-server.html

Language server for Taplo, a TOML toolkit.

taplo-cli can be installed via cargo:

cargo install --features lsp --locked taplo-cli

Snippet to enable the language server:

require'lspconfig'.taplo.setup{}

Default config:

tblgen_lsp_server

https://mlir.llvm.org/docs/Tools/MLIRLSP/#tablegen-lsp-language-server--tblgen-lsp-server

The Language Server for the LLVM TableGen language

tblgen-lsp-server can be installed at the llvm-project repository (https://github.com/llvm/llvm-project)

Snippet to enable the language server:

require'lspconfig'.tblgen_lsp_server.setup{}

Default config:

teal_ls

https://github.com/teal-language/teal-language-server

Install with:

luarocks install teal-language-server

Optional Command Args:

  • "--log-mode=by_date" - Enable logging in $HOME/.cache/teal-language-server. Log name will be date + pid of process
  • "--log-mode=by_proj_path" - Enable logging in $HOME/.cache/teal-language-server. Log name will be project path + pid of process
  • "--verbose=true" - Increases log level. Does nothing unless log-mode is set

Snippet to enable the language server:

require'lspconfig'.teal_ls.setup{}

Default config:

templ

https://templ.guide

The official language server for the templ HTML templating language.

Snippet to enable the language server:

require'lspconfig'.templ.setup{}

Default config:

terraform_lsp

https://github.com/juliosueiras/terraform-lsp

Terraform language server Download a released binary from https://github.com/juliosueiras/terraform-lsp/releases.

From https://github.com/hashicorp/terraform-ls#terraform-ls-vs-terraform-lsp:

Both HashiCorp and the maintainer of terraform-lsp expressed interest in collaborating on a language server and are working towards a long-term goal of a single stable and feature-complete implementation.

For the time being both projects continue to exist, giving users the choice:

  • terraform-ls providing

    • overall stability (by relying only on public APIs)
    • compatibility with any provider and any Terraform >=0.12.0 currently less features
    • due to project being younger and relying on public APIs which may not offer the same functionality yet

  • terraform-lsp providing

    • currently more features
    • compatibility with a single particular Terraform (0.12.20 at time of writing)
      • configs designed for other 0.12 versions may work, but interpretation may be inaccurate
    • less stability (due to reliance on Terraform's own internal packages)

Snippet to enable the language server:

require'lspconfig'.terraform_lsp.setup{}

Default config:

terraformls

https://github.com/hashicorp/terraform-ls

Terraform language server Download a released binary from https://github.com/hashicorp/terraform-ls/releases.

From https://github.com/hashicorp/terraform-ls#terraform-ls-vs-terraform-lsp:

Both HashiCorp and the maintainer of terraform-lsp expressed interest in collaborating on a language server and are working towards a long-term goal of a single stable and feature-complete implementation.

For the time being both projects continue to exist, giving users the choice:

  • terraform-ls providing

    • overall stability (by relying only on public APIs)
    • compatibility with any provider and any Terraform >=0.12.0 currently less features
    • due to project being younger and relying on public APIs which may not offer the same functionality yet

  • terraform-lsp providing

    • currently more features
    • compatibility with a single particular Terraform (0.12.20 at time of writing)
      • configs designed for other 0.12 versions may work, but interpretation may be inaccurate
    • less stability (due to reliance on Terraform's own internal packages)

Note, that the settings configuration option uses the workspace/didChangeConfiguration event, which is not supported by terraform-ls. Instead you should use init_options which passes the settings as part of the LSP initialize call as is required by terraform-ls.

Snippet to enable the language server:

require'lspconfig'.terraformls.setup{}

Default config:

texlab

https://github.com/latex-lsp/texlab

A completion engine built from scratch for (La)TeX.

See https://github.com/latex-lsp/texlab/wiki/Configuration for configuration options.

Snippet to enable the language server:

require'lspconfig'.texlab.setup{}

Commands:

  • TexlabBuild: Build the current buffer
  • TexlabCancelBuild: Cancel the current build
  • TexlabChangeEnvironment: Change the environment at current position
  • TexlabCleanArtifacts: Clean the artifacts
  • TexlabCleanAuxiliary: Clean the auxiliary files
  • TexlabDependencyGraph: Show the dependency graph
  • TexlabFindEnvironments: Find the environments at current position
  • TexlabForward: Forward search from current position

Default config:

  • cmd : 
    { "texlab" }
  • filetypes : 
    { "tex", "plaintex", "bib" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/texlab.lua:159
  • settings : 
    {
  texlab = {
    bibtexFormatter = "texlab",
    build = {
      args = { "-pdf", "-interaction=nonstopmode", "-synctex=1", "%f" },
      executable = "latexmk",
      forwardSearchAfter = false,
      onSave = false
    },
    chktex = {
      onEdit = false,
      onOpenAndSave = false
    },
    diagnosticsDelay = 300,
    formatterLineLength = 80,
    forwardSearch = {
      args = {}
    },
    latexFormatter = "latexindent",
    latexindent = {
      modifyLineBreaks = false
    }
  }
}
  • single_file_support : true

textlsp

https://github.com/hangyav/textLSP

textLSP is an LSP server for text spell and grammar checking with various AI tools. It supports multiple text file formats, such as LaTeX, Org or txt.

For the available text analyzer tools and their configuration, see the GitHub page. By default, all analyzers are disabled in textLSP, since most of them need special settings. For quick testing, LanguageTool is enabled in the default nvim-lspconfig configuration.

To install run: pip install textLSP

Snippet to enable the language server:

require'lspconfig'.textlsp.setup{}

Default config:

  • cmd : 
    { "textlsp" }
  • filetypes : 
    { "text", "tex", "org" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/textlsp.lua:2
  • settings : 
    {
  textLSP = {
    analysers = {
      languagetool = {
        check_text = {
          on_change = false,
          on_open = true,
          on_save = true
        },
        enabled = true
      }
    },
    documents = {
      org = {
        org_todo_keywords = { "TODO", "IN_PROGRESS", "DONE" }
      }
    }
  }
}
  • single_file_support : true

tflint

https://github.com/terraform-linters/tflint

A pluggable Terraform linter that can act as lsp server. Installation instructions can be found in https://github.com/terraform-linters/tflint#installation.

Snippet to enable the language server:

require'lspconfig'.tflint.setup{}

Default config:

theme_check

https://github.com/Shopify/shopify-cli

theme-check-language-server is bundled with shopify-cli or it can also be installed via

https://github.com/Shopify/theme-check#installation

NOTE: If installed via Homebrew, cmd must be set to 'theme-check-liquid-server'

require lspconfig.theme_check.setup {
  cmd = { 'theme-check-liquid-server' }
}

Snippet to enable the language server:

require'lspconfig'.theme_check.setup{}

Default config:

thriftls

https://github.com/joyme123/thrift-ls

you can install thriftls by mason or download binary here: https://github.com/joyme123/thrift-ls/releases

Snippet to enable the language server:

require'lspconfig'.thriftls.setup{}

Default config:

tilt_ls

https://github.com/tilt-dev/tilt

Tilt language server.

You might need to add filetype detection manually:

autocmd BufRead Tiltfile setf=tiltfile

Snippet to enable the language server:

require'lspconfig'.tilt_ls.setup{}

Default config:

tinymist

https://github.com/Myriad-Dreamin/tinymist An integrated language service for Typst [taɪpst]. You can also call it "微霭" [wēi ǎi] in Chinese.

Snippet to enable the language server:

require'lspconfig'.tinymist.setup{}

Default config:

ts_ls

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:

npm install -g typescript typescript-language-server

To configure typescript language server, add a tsconfig.json or jsconfig.json to the root of your project.

Here's an example that disables type checking in JavaScript files.

{
  "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.

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.

Snippet to enable the language server:

require'lspconfig'.ts_ls.setup{}

Default config:

  • cmd : 
    { "typescript-language-server", "--stdio" }
  • filetypes : 
    { "javascript", "javascriptreact", "javascript.jsx", "typescript", "typescriptreact", "typescript.tsx" }
  • init_options : 
    {
  hostInfo = "neovim"
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/ts_ls.lua:4
  • single_file_support : true

ts_query_ls

https://github.com/ribru17/ts_query_ls Can be configured by passing a "settings" object to ts_query_ls.setup{}:

require('lspconfig').ts_query_ls.setup{
    settings = {
      parser_install_directories = {
        -- If using nvim-treesitter with lazy.nvim
        vim.fs.joinpath(
          vim.fn.stdpath('data'),
          '/lazy/nvim-treesitter/parser/'
        ),
      },
      -- This setting is provided by default
      parser_aliases = {
        ecma = 'javascript',
        jsx = 'javascript',
        php_only = 'php',
      },
      -- E.g. zed support
      language_retrieval_patterns = {
        'languages/src/([^/]+)/[^/]+\\.scm$',
      },
    },
}

Snippet to enable the language server:

require'lspconfig'.ts_query_ls.setup{}

Default config:

  • cmd : 
    { "ts_query_ls" }
  • filetypes : 
    { "query" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/ts_query_ls.lua:4
  • settings : 
    {
  parser_aliases = {
    ecma = "javascript",
    jsx = "javascript",
    php_only = "php"
  }
}

tsp_server

https://github.com/microsoft/typespec

The language server for TypeSpec, a language for defining cloud service APIs and shapes.

tsp-server can be installed together with the typespec compiler via npm:

npm install -g @typespec/compiler

Snippet to enable the language server:

require'lspconfig'.tsp_server.setup{}

Default config:

ttags

https://github.com/npezza93/ttags

Snippet to enable the language server:

require'lspconfig'.ttags.setup{}

Default config:

turtle_ls

https://github.com/stardog-union/stardog-language-servers/tree/master/packages/turtle-language-server turtle-language-server, An editor-agnostic server providing language intelligence (diagnostics, hover tooltips, etc.) for the W3C standard Turtle RDF syntax via the Language Server Protocol. installable via npm install -g turtle-language-server or yarn global add turtle-language-server. requires node.

Snippet to enable the language server:

require'lspconfig'.turtle_ls.setup{}

Default config:

tvm_ffi_navigator

https://github.com/tqchen/ffi-navigator

The Language Server for FFI calls in TVM to be able jump between python and C++

FFI navigator can be installed with pip install ffi-navigator, buf for more details, please see https://github.com/tqchen/ffi-navigator?tab=readme-ov-file#installation

Snippet to enable the language server:

require'lspconfig'.tvm_ffi_navigator.setup{}

Default config:

twiggy_language_server

https://github.com/moetelo/twiggy

twiggy-language-server can be installed via npm:

npm install -g twiggy-language-server

Snippet to enable the language server:

require'lspconfig'.twiggy_language_server.setup{}

Default config:

typeprof

https://github.com/ruby/typeprof

typeprof is the built-in analysis and LSP tool for Ruby 3.1+.

Snippet to enable the language server:

require'lspconfig'.typeprof.setup{}

Default config:

typos_lsp

https://github.com/crate-ci/typos https://github.com/tekumara/typos-lsp

A Language Server Protocol implementation for Typos, a low false-positive source code spell checker, written in Rust. Download it from the releases page on GitHub: https://github.com/tekumara/typos-lsp/releases

Snippet to enable the language server:

require'lspconfig'.typos_lsp.setup{}

Default config:

typst_lsp

https://github.com/nvarner/typst-lsp

Language server for Typst.

Snippet to enable the language server:

require'lspconfig'.typst_lsp.setup{}

Default config:

uiua

https://github.com/uiua-lang/uiua/

The builtin language server of the Uiua interpreter.

The Uiua interpreter can be installed with cargo install uiua

Snippet to enable the language server:

require'lspconfig'.uiua.setup{}

Default config:

ungrammar_languageserver

https://github.com/binhtran432k/ungrammar-language-features Language Server for Ungrammar.

Ungrammar Language Server can be installed via npm:

npm i ungrammar-languageserver -g

Snippet to enable the language server:

require'lspconfig'.ungrammar_languageserver.setup{}

Default config:

  • cmd : 
    { "ungrammar-languageserver", "--stdio" }
  • filetypes : 
    { "ungrammar" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/ungrammar_languageserver.lua:2
  • settings : 
    {
  ungrammar = {
    format = {
      enable = true
    },
    validate = {
      enable = true
    }
  }
}
  • single_file_support : true

unison

https://github.com/unisonweb/unison/blob/trunk/docs/language-server.markdown

Snippet to enable the language server:

require'lspconfig'.unison.setup{}

Default config:

unocss

https://github.com/xna00/unocss-language-server

UnoCSS Language Server can be installed via npm:

npm i unocss-language-server -g

Snippet to enable the language server:

require'lspconfig'.unocss.setup{}

Default config:

  • cmd : 
    { "unocss-language-server", "--stdio" }
  • filetypes : 
    { "erb", "haml", "hbs", "html", "css", "postcss", "javascript", "javascriptreact", "markdown", "ejs", "php", "svelte", "typescript", "typescriptreact", "vue-html", "vue", "sass", "scss", "less", "stylus", "astro", "rescript", "rust" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/unocss.lua:4

uvls

https://codeberg.org/caradhras/uvls Language server for UVL, written using tree sitter and rust. You can install the server easily using cargo:

git clone https://codeberg.org/caradhras/uvls
cd  uvls
cargo install --path .

Note: To activate properly nvim needs to know the uvl filetype. You can add it via:

vim.cmd([[au BufRead,BufNewFile *.uvl setfiletype uvl]])

Snippet to enable the language server:

require'lspconfig'.uvls.setup{}

Default config:

v_analyzer

https://github.com/vlang/v-analyzer

V language server.

v-analyzer can be installed by following the instructions here.

Snippet to enable the language server:

require'lspconfig'.v_analyzer.setup{}

Default config:

vacuum

Vacuum is the worlds fastest OpenAPI 3, OpenAPI 2 / Swagger linter and quality analysis tool.

You can install vacuum using mason or follow the instructions here: https://github.com/daveshanley/vacuum

The file types are not detected automatically, you can register them manually (see below) or override the filetypes:

vim.filetype.add {
  pattern = {
    ['openapi.*%.ya?ml'] = 'yaml.openapi',
    ['openapi.*%.json'] = 'json.openapi',
  },
}

Snippet to enable the language server:

require'lspconfig'.vacuum.setup{}

Default config:

  • cmd : 
    { "vacuum", "language-server" }
  • filetypes : 
    { "yaml.openapi", "json.openapi" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/vacuum.lua:2
  • single_file_support : true

vala_ls

https://github.com/Prince781/vala-language-server

Snippet to enable the language server:

require'lspconfig'.vala_ls.setup{}

Default config:

vale_ls

https://github.com/errata-ai/vale-ls

An implementation of the Language Server Protocol (LSP) for the Vale command-line tool.

Snippet to enable the language server:

require'lspconfig'.vale_ls.setup{}

Default config:

vdmj

https://github.com/nickbattle/vdmj

The VDMJ language server can be installed by cloning the VDMJ repository and running mvn clean install.

Various options are provided to configure the language server (see below). In particular:

  • annotation_paths is a list of folders and/or jar file paths for annotations that should be used with the language server;
  • any value of debugger_port less than zero will disable the debugger; note that if a non-zero value is used, only one instance of the server can be active at a time.

More settings for VDMJ can be changed in a file called vdmj.properties under root_dir/.vscode. For a description of the available settings, see Section 7 of the VDMJ User Guide.

Note: proof obligations and combinatorial testing are not currently supported by neovim.

Snippet to enable the language server:

require'lspconfig'.vdmj.setup{}

Default config:

  • cmd : 
    { "java" }
  • filetypes : 
    { "vdmsl", "vdmpp", "vdmrt" }
  • options : 
    {
  annotation_paths = {},
  debugger_port = -1,
  high_precision = false,
  java = "/usr/lib/jvm/temurin-17-jdk-amd64/bin/java",
  java_opts = { "-Xmx3000m", "-Xss1m" },
  logfile = "/home/user/.cache/nvim/vdm-lsp.log",
  mavenrepo = "/home/user/.m2/repository/com/fujitsu"
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/vdmj.lua:44

verible

https://github.com/chipsalliance/verible

A linter and formatter for verilog and SystemVerilog files.

Release binaries can be downloaded from here and placed in a directory on PATH.

See https://github.com/chipsalliance/verible/tree/master/verilog/tools/ls/README.md for options.

Snippet to enable the language server:

require'lspconfig'.verible.setup{}

Default config:

veridian

https://github.com/vivekmalneedi/veridian

A SystemVerilog LanguageServer.

Download the latest release for your OS from the releases page

install with slang feature, if C++17 compiler is available

cargo install --git https://github.com/vivekmalneedi/veridian.git --all-features

install if C++17 compiler is not available

cargo install --git https://github.com/vivekmalneedi/veridian.git

Snippet to enable the language server:

require'lspconfig'.veridian.setup{}

Default config:

veryl_ls

https://github.com/veryl-lang/veryl

Language server for Veryl

veryl-ls can be installed via cargo:

cargo install veryl-ls

Snippet to enable the language server:

require'lspconfig'.veryl_ls.setup{}

Default config:

vhdl_ls

Install vhdl_ls from https://github.com/VHDL-LS/rust_hdl and add it to path

Configuration

The language server needs to know your library mapping to perform full analysis of the code. For this it uses a configuration file in the TOML format named vhdl_ls.toml.

vhdl_ls will load configuration files in the following order of priority (first to last):

A file named .vhdl_ls.toml in the user home folder.
A file name from the VHDL_LS_CONFIG environment variable.
A file named vhdl_ls.toml in the workspace root.

Settings in a later files overwrites those from previously loaded files.

Example vhdl_ls.toml

# File names are either absolute or relative to the parent folder of the vhdl_ls.toml file
[libraries]
lib2.files = [
  'pkg2.vhd',
]
lib1.files = [
  'pkg1.vhd',
  'tb_ent.vhd'
]

Snippet to enable the language server:

require'lspconfig'.vhdl_ls.setup{}

Default config:

vimls

https://github.com/iamcco/vim-language-server

You can install vim-language-server via npm:

npm install -g vim-language-server

Snippet to enable the language server:

require'lspconfig'.vimls.setup{}

Default config:

  • cmd : 
    { "vim-language-server", "--stdio" }
  • filetypes : 
    { "vim" }
  • init_options : 
    {
  diagnostic = {
    enable = true
  },
  indexes = {
    count = 3,
    gap = 100,
    projectRootPatterns = { "runtime", "nvim", ".git", "autoload", "plugin" },
    runtimepath = true
  },
  isNeovim = true,
  iskeyword = "@,48-57,_,192-255,-#",
  runtimepath = "",
  suggest = {
    fromRuntimepath = true,
    fromVimruntime = true
  },
  vimruntime = ""
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/vimls.lua:2
  • single_file_support : true

visualforce_ls

https://github.com/forcedotcom/salesforcedx-vscode

Language server for Visualforce.

For manual installation, download the .vsix archive file from the forcedotcom/salesforcedx-vscode GitHub releases. Then, configure cmd to run the Node script at the unpacked location:

require'lspconfig'.visualforce_ls.setup {
  cmd = {
    'node',
    '/path/to/unpacked/archive/extension/node_modules/@salesforce/salesforcedx-visualforce-language-server/out/src/visualforceServer.js',
    '--stdio'
  }
}

Snippet to enable the language server:

require'lspconfig'.visualforce_ls.setup{}

Default config:

vls

https://github.com/vlang/vls

V language server.

v-language-server can be installed by following the instructions here.

Snippet to enable the language server:

require'lspconfig'.vls.setup{}

Default config:

volar

https://github.com/vuejs/language-tools/tree/master/packages/language-server

Volar language server for Vue

Volar can be installed via npm:

npm install -g @vue/language-server

Volar by default supports Vue 3 projects. For Vue 2 projects, additional configuration are required.

Hybrid Mode (by default)

In this mode, the Vue Language Server exclusively manages the CSS/HTML sections. You need the ts_ls server with the @vue/typescript-plugin plugin to support TypeScript in .vue files. See ts_ls section for more information

No Hybrid Mode

Volar will run embedded ts_ls therefore there is no need to run it separately.

local lspconfig = require('lspconfig')

lspconfig.volar.setup {
  -- add filetypes for typescript, javascript and vue
  filetypes = { 'typescript', 'javascript', 'javascriptreact', 'typescriptreact', 'vue' },
  init_options = {
    vue = {
      -- disable hybrid mode
      hybridMode = false,
    },
  },
}
-- you must remove ts_ls setup
-- lspconfig.ts_ls.setup {}

Overriding the default TypeScript Server used by Volar

The default config looks for TypeScript in the local node_modules. This can lead to issues e.g. when working on a monorepo. The alternatives are:

  • use a global TypeScript Server installation
require'lspconfig'.volar.setup {
  init_options = {
    typescript = {
      -- replace with your global TypeScript library path
      tsdk = '/path/to/node_modules/typescript/lib'
    }
  }
}
  • use a local server and fall back to a global TypeScript Server installation
require'lspconfig'.volar.setup {
  init_options = {
    typescript = {
      -- replace with your global TypeScript library path
      tsdk = '/path/to/node_modules/typescript/lib'
    }
  },
  on_new_config = function(new_config, new_root_dir)
    local lib_path = vim.fs.find('node_modules/typescript/lib', { path = new_root_dir, upward = true })[1]
    if lib_path then
      new_config.init_options.typescript.tsdk = lib_path
    end
  end
}

Snippet to enable the language server:

require'lspconfig'.volar.setup{}

Default config:

vscoqtop

https://github.com/coq-community/vscoq

Snippet to enable the language server:

require'lspconfig'.vscoqtop.setup{}

Default config:

vtsls

https://github.com/yioneko/vtsls

vtsls can be installed with npm:

npm install -g @vtsls/language-server

To configure a TypeScript project, add a tsconfig.json or jsconfig.json to the root of your project.

Snippet to enable the language server:

require'lspconfig'.vtsls.setup{}

Default config:

  • cmd : 
    { "vtsls", "--stdio" }
  • filetypes : 
    { "javascript", "javascriptreact", "javascript.jsx", "typescript", "typescriptreact", "typescript.tsx" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/vtsls.lua:4
  • single_file_support : true

vuels

https://github.com/vuejs/vetur/tree/master/server

Vue language server(vls) vue-language-server can be installed via npm:

npm install -g vls

Snippet to enable the language server:

require'lspconfig'.vuels.setup{}

Default config:

  • cmd : 
    { "vls" }
  • filetypes : 
    { "vue" }
  • init_options : 
    {
  config = {
    css = {},
    emmet = {},
    html = {
      suggest = {}
    },
    javascript = {
      format = {}
    },
    stylusSupremacy = {},
    typescript = {
      format = {}
    },
    vetur = {
      completion = {
        autoImport = false,
        tagCasing = "kebab",
        useScaffoldSnippets = false
      },
      format = {
        defaultFormatter = {
          js = "none",
          ts = "none"
        },
        defaultFormatterOptions = {},
        scriptInitialIndent = false,
        styleInitialIndent = false
      },
      useWorkspaceDependencies = false,
      validation = {
        script = true,
        style = true,
        template = true
      }
    }
  }
}
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/vuels.lua:4

wgsl_analyzer

https://github.com/wgsl-analyzer/wgsl-analyzer

wgsl_analyzer can be installed via cargo:

cargo install --git https://github.com/wgsl-analyzer/wgsl-analyzer wgsl_analyzer

Snippet to enable the language server:

require'lspconfig'.wgsl_analyzer.setup{}

Default config:

yamlls

https://github.com/redhat-developer/yaml-language-server

yaml-language-server can be installed via yarn:

yarn global add yaml-language-server

To use a schema for validation, there are two options:

  1. Add a modeline to the file. A modeline is a comment of the form:
# yaml-language-server: $schema=<urlToTheSchema|relativeFilePath|absoluteFilePath}>

where the relative filepath is the path relative to the open yaml file, and the absolute filepath is the filepath relative to the filesystem root ('/' on unix systems)

  1. Associated a schema url, relative , or absolute (to root of project, not to filesystem root) path to the a glob pattern relative to the detected project root. Check :LspInfo to determine the resolved project root.
require('lspconfig').yamlls.setup {
  ... -- other configuration for setup {}
  settings = {
    yaml = {
      ... -- other settings. note this overrides the lspconfig defaults.
      schemas = {
        ["https://json.schemastore.org/github-workflow.json"] = "/.github/workflows/*",
        ["../path/relative/to/file.yml"] = "/.github/workflows/*",
        ["/path/from/root/of/project"] = "/.github/workflows/*",
      },
    },
  }
}

Currently, kubernetes is special-cased in yammls, see the following upstream issues:

To override a schema to use a specific k8s schema version (for example, to use 1.18):

require('lspconfig').yamlls.setup {
  ... -- other configuration for setup {}
  settings = {
    yaml = {
      ... -- other settings. note this overrides the lspconfig defaults.
      schemas = {
        ["https://raw.githubusercontent.com/yannh/kubernetes-json-schema/refs/heads/master/v1.32.1-standalone-strict/all.json"] = "/*.k8s.yaml",
        ... -- other schemas
      },
    },
  }
}

Snippet to enable the language server:

require'lspconfig'.yamlls.setup{}

Default config:

  • cmd : 
    { "yaml-language-server", "--stdio" }
  • filetypes : 
    { "yaml", "yaml.docker-compose", "yaml.gitlab" }
  • root_dir source (use "gF" to visit): ../lua/lspconfig/configs/yamlls.lua:2
  • settings : 
    {
  redhat = {
    telemetry = {
      enabled = false
    }
  }
}
  • single_file_support : true

yang_lsp

https://github.com/TypeFox/yang-lsp

A Language Server for the YANG data modeling language.

Snippet to enable the language server:

require'lspconfig'.yang_lsp.setup{}

Default config:

yls

https://pypi.org/project/yls-yara/

An YLS plugin adding YARA linting capabilities.

This plugin runs yara.compile on every save, parses the errors, and returns list of diagnostic messages.

Language Server: https://github.com/avast/yls

Snippet to enable the language server:

require'lspconfig'.yls.setup{}

Default config:

ziggy

https://ziggy-lang.io/documentation/ziggy-lsp/

Language server for the Ziggy data serialization format

Snippet to enable the language server:

require'lspconfig'.ziggy.setup{}

Default config:

ziggy_schema

https://ziggy-lang.io/documentation/ziggy-lsp/

Language server for schema files of the Ziggy data serialization format

Snippet to enable the language server:

require'lspconfig'.ziggy_schema.setup{}

Default config:

zk

https://github.com/mickael-menu/zk

A plain text note-taking assistant

Snippet to enable the language server:

require'lspconfig'.zk.setup{}

Commands:

  • ZkIndex: ZkIndex
  • ZkList: ZkList
  • ZkNew: ZkNew

Default config:

zls

https://github.com/zigtools/zls

Zig LSP implementation + Zig Language Server

Snippet to enable the language server:

require'lspconfig'.zls.setup{}

Default config: