Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
clickhouse avatar

Typescript Lsp

  • 23 installs
  • 326 repo stars
  • Updated August 4, 2026
  • clickhouse/clickhouse-js

Use the TypeScript language server in the clickhouse-js repo for go-to-definition, find references, hover types, symbol search, and per-file diagnostics.

About

Uses the typescript-language-server for precise code intelligence in the clickhouse-js repo: definitions, references, hover types, symbol search, and diagnostics. A developer uses it instead of grep to resolve symbols and inspect inferred types across the workspaces.

  • Preferred over grep for resolving definitions and usages
  • Requires npm install (setup skill) to populate node_modules

Typescript Lsp by the numbers

  • 23 all-time installs (skills.sh)
  • Ranked #710 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/clickhouse/clickhouse-js --skill typescript-lsp

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs23
repo stars326
Last updatedAugust 4, 2026
Repositoryclickhouse/clickhouse-js

What it does

Use the TypeScript language server in the clickhouse-js repo for go-to-definition, find references, hover types, symbol search, and per-file diagnostics.

Files

SKILL.mdMarkdownGitHub ↗

TypeScript Language Server in clickhouse-js

typescript-language-server is declared as a root devDependency, so after npm install (see the setup skill) it is available via npx and uses the workspace-local typescript (6.x) compiler, matching CI exactly.

Starting the server

From the repo root:

npx typescript-language-server --stdio

It speaks LSP (JSON-RPC, Content-Length-framed) over stdio. There is no extra configuration: each packages/* workspace, tests/clickhouse-test-runner, examples/node, and examples/web has its own tsconfig.json, and the server picks the nearest one per opened file automatically.

Protocol essentials

1. Send initialize with rootUri/workspaceFolders pointing at the repo root, then the initialized notification. 2. Send textDocument/didOpen with the full file text for every file you want to query (the server reads dependencies from disk on its own; only files you query positions in need to be opened). 3. Positions are 0-based (line and character).

Verified capabilities (typescript-language-server 5.x, TS 6.x)

RequestNotes
textDocument/hoverReturns the full inferred signature + JSDoc markdown
textDocument/definitionResolves across workspace packages via source, not dist/
textDocument/referencesWithin the opened file's project
workspace/symbole.g. query ClickHouseClient finds class + re-exports
textDocument/completionContext-aware member completions
DiagnosticsPush only (textDocument/publishDiagnostics notifications, sent ~1–3s after didOpen). The pull textDocument/diagnostic request is _not_ supported (-32601) — wait for the push notification instead.

Tips

  • If your environment provides built-in LSP/code-intelligence tooling, point

it at npx typescript-language-server --stdio with the repo root as the workspace folder.

  • For one-off scripted queries, spawn the server from Node, frame messages

with Content-Length: <bytes>\r\n\r\n<json>, and match responses by id.

  • A full workspace typecheck is still npm run build && npm run typecheck

(build first — some workspaces import compiled dist/ outputs); the LSP is for targeted, interactive queries, not for CI-equivalent validation.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.