LSP Configuration

GentlemanNvim leverages LazyVim’s LSP configuration with additional language support and custom settings for frontend development.

Overview

The LSP setup is managed through LazyVim extras, providing:

Auto-installation

LSP servers install automatically on first use

Multiple Languages

TypeScript, Go, Nix, JSON, TOML, and more

Format on Save

Prettier and Biome integration

Inline Diagnostics

Real-time error checking

Enabled Language Servers

Configured through LazyVim extras in config/lazy.lua:

TypeScript & JavaScript

{ import = "lazyvim.plugins.extras.lang.typescript" }
{ import = "lazyvim.plugins.extras.lang.angular" }

Provides:

tsserver - TypeScript language server
Angular Language Service - Angular-specific IntelliSense
Type checking and auto-imports
Refactoring support

TypeScript Features

Go to definition/references
Rename symbol across project
Organize imports
Quick fixes and code actions
Inlay hints for types
Auto-completion with type information

JSON

{ import = "lazyvim.plugins.extras.lang.json" }

Provides:

jsonls - JSON language server
Schema validation
Auto-completion for package.json, tsconfig.json, etc.

Markdown

{ import = "lazyvim.plugins.extras.lang.markdown" }

Provides:

marksman - Markdown language server
Link validation
Table of contents generation
Reference completion

Enhanced with:

{ "MeanderingProgrammer/render-markdown.nvim" }

Go

{ import = "lazyvim.plugins.extras.lang.go" }

Provides:

gopls - Official Go language server
Code formatting with gofmt
Import organization
Test integration

Other Languages

Extra	Language Server	Purpose
`lang.astro`	astro-ls	Astro framework support
`lang.nix`	nil	Nix language support
`lang.toml`	taplo	TOML configuration files

Formatters

Prettier

{ import = "lazyvim.plugins.extras.formatting.prettier" }

Formats:

JavaScript/TypeScript
JSON
Markdown
HTML/CSS
YAML

Configuration: Prettier looks for .prettierrc in your project root. Default settings apply if not found.

Create a .prettierrc.json in your project to customize formatting:

{
  "semi": true,
  "singleQuote": true,
  "tabWidth": 2,
  "printWidth": 100
}

Biome

{ import = "lazyvim.plugins.extras.formatting.biome" }

Fast alternative to Prettier for JavaScript/TypeScript:

10-20x faster than Prettier
Integrated linter
Compatible with Prettier configs

When Biome is used: Biome takes precedence when biome.json exists in project root.

Biome and Prettier coexist - Biome is used when configured, otherwise Prettier is the fallback.

Linters

ESLint

{ import = "lazyvim.plugins.extras.linting.eslint" }

JavaScript/TypeScript linting with:

Real-time error highlighting
Code action fixes
Auto-fix on save (when configured)

Configuration: ESLint requires configuration in your project:

.eslintrc.js
.eslintrc.json
eslint.config.js (flat config)

ESLint will not run without a configuration file. Create one in your project root or run npm init @eslint/config.

LSP Keybindings

Inherited from LazyVim:

Keymap	Action	Description
`gd`	Go to definition	Jump to where symbol is defined
`gr`	Go to references	Show all references
`gI`	Go to implementation	Jump to implementation
`gy`	Go to type definition	Jump to type definition
`K`	Hover documentation	Show documentation popup

Code Actions

Keymap	Action	Description
`<leader>ca`	Code actions	Show available code actions
`<leader>rn`	Rename	Rename symbol project-wide
`<leader>cf`	Format	Format current buffer
`<leader>cF`	Format injected	Format injected code (e.g., in markdown)

Diagnostics

Keymap	Action	Description
`]d`	Next diagnostic	Jump to next error/warning
`[d`	Previous diagnostic	Jump to previous error/warning
`<leader>cd`	Line diagnostics	Show diagnostics for current line
`<leader>xx`	Trouble	Open trouble list (all diagnostics)

Custom LSP Configuration

Node.js Integration

Custom Node.js host configuration:

vim.g.node_host_prog = vim.fn.exepath("node") or "/usr/local/bin/node"

if vim.fn.executable("node") == 1 then
  local node_version = vim.fn.system("node --version"):gsub("\n", "")
  print("Using Node.js version: " .. node_version)
end

The configuration automatically detects and uses the Node.js in your PATH. Required for:

TypeScript language server
ESLint
Prettier
Angular Language Service

LSP on Attach

LazyVim automatically sets up LSP keybindings when a language server attaches. No additional configuration needed.

Completion Engine

Blink.cmp

Modern completion engine replacing nvim-cmp:

{ import = "lazyvim.plugins.extras.coding.blink" }

Features:

Faster than nvim-cmp
LSP completion
Snippet support
Fuzzy matching
AI assistant completion (Avante integration)

Custom Sources:

opts = {
  sources = {
    default = { "avante_commands", "avante_mentions", "avante_files" },
    providers = {
      avante_commands = { score_offset = 90 },
      avante_files = { score_offset = 100 },
      avante_mentions = { score_offset = 1000 },
    },
  },
}

Completion Sources Priority

avante_mentions (score: 1000) - @mentions in AI chat
avante_files (score: 100) - File paths
avante_commands (score: 90) - AI commands
LSP (score: 60) - Language server completions
Buffer - Words from current buffer
Path - File system paths

Copilot Integration

GitHub Copilot completions are integrated but disabled in specific file types:

require("copilot.api").filetypes = {
  yaml = false,
  markdown = false,
  help = false,
  gitcommit = false,
  gitrebase = false,
}

Copilot is intentionally disabled in documentation and configuration files to prevent unwanted AI suggestions.

Format on Save

LazyVim automatically formats on save using configured formatters:

Biome (if biome.json exists)
Prettier (fallback for JS/TS/JSON/MD)
LSP formatter (language-specific)

Disable Format on Save

Per-buffer:

:lua vim.b.autoformat = false

Globally in config:

vim.g.autoformat = false

Diagnostic Configuration

LazyVim provides sensible diagnostic defaults:

Diagnostic Settings

vim.diagnostic.config({
  virtual_text = true,        -- Show errors inline
  signs = true,               -- Show signs in gutter
  update_in_insert = false,   -- Don't update while typing
  underline = true,           -- Underline errors
  severity_sort = true,       -- Sort by severity
})

LSP Server Management

Mason

LazyVim uses Mason to manage LSP servers:

Command	Action
`:Mason`	Open Mason UI
`:MasonInstall <server>`	Install LSP server
`:MasonUninstall <server>`	Uninstall LSP server
`:MasonUpdate`	Update all installed servers

LazyVim auto-installs LSP servers when you open a file. You rarely need to use Mason manually.

Commonly Installed Servers

These install automatically based on file types:

typescript-language-server - TypeScript/JavaScript
angular-language-server - Angular
json-lsp - JSON
marksman - Markdown
gopls - Go
nil - Nix
taplo - TOML
lua-language-server - Lua

Troubleshooting

LSP Not Starting

Check LSP Status

Run :LspInfo to see active servers and their status

Check Mason

Run :Mason to verify the language server is installed

Check Logs

Run :LspLog to view language server logs

Restart LSP

Run :LspRestart to restart the language server

Formatting Not Working

Verify Formatter Installation

Check if Prettier/Biome is in your project:

npm list prettier biome

Check Autoformat Setting

Run in Neovim:

:lua print(vim.b.autoformat, vim.g.autoformat)

Both should be true or nil

Manual Format

Try formatting manually with <leader>cf to see errors

ESLint Not Running

ESLint requires a configuration file (.eslintrc.js, .eslintrc.json, or eslint.config.js) in your project root.

Create configuration:

npm init @eslint/config

Advanced Configuration

Custom LSP Settings

Override LSP server settings by creating lua/plugins/lsp.lua:

return {
  {
    "neovim/nvim-lspconfig",
    opts = {
      servers = {
        tsserver = {
          settings = {
            typescript = {
              inlayHints = {
                includeInlayParameterNameHints = "all",
                includeInlayFunctionParameterTypeHints = true,
              },
            },
          },
        },
      },
    },
  },
}

Add Custom Language Server

Example for adding a new LSP:

return {
  {
    "neovim/nvim-lspconfig",
    opts = {
      servers = {
        -- Add your custom server
        rust_analyzer = {
          settings = {
            ["rust-analyzer"] = {
              cargo = {
                allFeatures = true,
              },
            },
          },
        },
      },
    },
  },
}

Performance Tips

For large TypeScript projects:

Create tsconfig.json with strict file includes
Use project references for monorepos

Consider disabling semantic tokens:

tsserver = {
  settings = {
    typescript = {
      semanticTokens = { enabled = false },
    },
  },
}

Get Started

Terminal Emulators

Shells

Window Managers

Neovim Configuration

AI Integration

Platform-Specific Guides

Advanced

​LSP Configuration

​Overview

Auto-installation

Multiple Languages

Format on Save

Inline Diagnostics

​Enabled Language Servers

​TypeScript & JavaScript

​JSON

​Markdown

​Go

​Other Languages

​Formatters

​Prettier

​Biome

​Linters

​ESLint

​LSP Keybindings

​Navigation

​Code Actions

​Diagnostics

​Custom LSP Configuration

​Node.js Integration

​LSP on Attach

​Completion Engine

​Blink.cmp

​Copilot Integration

​Format on Save

​Disable Format on Save

​Diagnostic Configuration

​LSP Server Management

​Mason

​Commonly Installed Servers

​Troubleshooting

​LSP Not Starting

​Formatting Not Working

​ESLint Not Running

​Advanced Configuration

​Custom LSP Settings

​Add Custom Language Server

​Performance Tips

​Next Steps

AI Assistants

Keymaps

Build docs developers (and LLMs) love

LSP Configuration

Overview

Enabled Language Servers

TypeScript & JavaScript

JSON

Markdown

Go

Other Languages

Formatters

Prettier

Biome

Linters

ESLint

LSP Keybindings

Navigation

Code Actions

Diagnostics

Custom LSP Configuration

Node.js Integration

LSP on Attach

Completion Engine

Blink.cmp

Copilot Integration

Format on Save

Disable Format on Save

Diagnostic Configuration

LSP Server Management

Mason

Commonly Installed Servers

Troubleshooting

LSP Not Starting

Formatting Not Working

ESLint Not Running

Advanced Configuration

Custom LSP Settings

Add Custom Language Server

Performance Tips

Next Steps