claudelint

Appearance

lsp-command-not-in-path ​

LSP server commands should be in PATH or use absolute paths

Warning

Rule Details ​

This rule checks each LSP server entry in lsp.json for its command field and warns when the command does not start with / (absolute path) or ./ (explicit relative path). Commands that rely on being in the system PATH may fail in environments where PATH is configured differently, such as CI systems, containers, or other developers' machines.

Incorrect ​

Server command relies on PATH resolution

json
{
  "typescript-server": {
    "command": "typescript-language-server --stdio"
  }
}

Correct ​

Server command uses absolute path

json
{
  "typescript-server": {
    "command": "/usr/local/bin/typescript-language-server --stdio"
  }
}

Server command uses explicit relative path

json
{
  "typescript-server": {
    "command": "./node_modules/.bin/typescript-language-server --stdio"
  }
}

How To Fix ​

Replace bare command names with absolute paths (e.g., /usr/local/bin/my-server) or explicit relative paths (e.g., ./node_modules/.bin/my-server). You can find the absolute path with which <command>.

Options ​

This rule does not have any configuration options.

When Not To Use It ​

Disable this rule if you have consistent PATH configuration across all environments and prefer shorter command references.

Resources ​

Version ​

Available since: v0.2.0