typescript-lsp
Use the TypeScript language server (typescript-language-server) for precise code intelligence in the clickhouse-js repository: go-to-definition, find references, hover (type signatures and JSDoc, including @deprecated info), workspace-wide symbol search, completions, and per-file type diagnostics. Prefer this over grep when you need to resolve a symbol's actual definition, find all usages of an exported API, or inspect inferred types across the packages/ workspaces. The server is preinstalled as a root devDependency — run the repository setup skill (npm install) first so nodemodules is populated. Do NOT use this skill for downstream projects that merely depend on @clickhouse/client; it is specific to working inside this repo.
- Installs
- 50
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/clickhouse/clickhouse-js --skill typescript-lsp- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads typescript-lsp automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.
The server (6.x) requires Node.js >= 22.22.2, newer than the repository's
Node 20 minimum; on Node 20 npm install only warns, but the server isn't supported there.
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
- Send
initializewithrootUri/workspaceFolderspointing at the repo root, then theinitializednotification. - Send
textDocument/didOpenwith 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). - Positions are 0-based (line and character).
Verified capabilities (typescript-language-server 5.x, TS 6.x)
| Request | Notes |
|---|---|
textDocument/hover | Returns the full inferred signature + JSDoc markdown |
textDocument/definition | Resolves across workspace packages via source, not dist/ |
textDocument/references | Within the opened file's project |
workspace/symbol | e.g. query ClickHouseClient finds class + re-exports |
textDocument/completion | Context-aware member completions |
| Diagnostics | Push 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 --stdiowith 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 byid. - A full workspace typecheck is still
npm run build && npm run typecheck(build first — some workspaces import compileddist/outputs); the LSP is for targeted, interactive queries, not for CI-equivalent validation.
FAQ
What does the typescript-lsp skill do?
Use the TypeScript language server (typescript-language-server) for precise code intelligence in the clickhouse-js repository: go-to-definition, find references, hover (type signatures and JSDoc, including @deprecated info), workspace-wide symbol search, completions, and per-file type diagnostics. Prefer this over grep when you need to resolve a symbol's actual definition, find all usages of an exported API, or inspect inferred types across the packages/ workspaces. The server is preinstalled as a root devDependency — run the repository setup skill (npm install) first so nodemodules is populated. Do NOT use this skill for downstream projects that merely depend on @clickhouse/client; it is specific to working inside this repo.
How do I install typescript-lsp?
Run npx skills add https://github.com/clickhouse/clickhouse-js --skill typescript-lsp in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/typescript-lsp/ (personal) or .claude/skills/typescript-lsp/ (project).
Which AI agents can use typescript-lsp?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is typescript-lsp safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains typescript-lsp?
It is published by clickhouse in clickhouse/clickhouse-js. It has 50 recorded installs.
More from clickhouse/clickhouse-js
clickhouse-js-node-troubleshooting
clickhouse/clickhouse-js
Troubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client). Use this skill whenever a user reports errors, unexpected behavior, or configuration questions involving the Node.js client specifically — including socket hang-up errors, Keep-Alive problems, stream handling issues, data type mismatches, read-only user restrictions, proxy/TLS setup problems, or long-running query timeouts. Trigger even when the user hasn't precisely named the issue; vague symptoms like "my inserts keep failing" or "connection drops randomly" in a Node.js context are strong signals to use this skill. Do NOT use for browser/Web client issues.
clickhouse-js-node-coding
clickhouse/clickhouse-js
Write idiomatic application code with the ClickHouse Node.js client (@clickhouse/client). Use this skill whenever a user is building against the Node.js client — configuring the client, pinging, inserting rows in JSON or raw formats, selecting and parsing results, binding query parameters, managing sessions and temporary tables, working with data types or customizing JSON parsing. Do NOT use for browser/Web client code.
setup
clickhouse/clickhouse-js
Set up the clickhouse-js repository in a fresh checkout so the agent can run tests, lints, type checks, builds, or examples. Use this skill before invoking any npm run test:, npm run lint, npm run typecheck, npm run build, or npm run run-examples script — or after pulling changes that touch any package.json (root, examples/node, or examples/web). Covers Node.js version requirements, installing dependencies across the npm workspaces and the two independent example packages, building the workspace packages so inter-package imports resolve, and starting ClickHouse via Docker Compose for integration tests. Do NOT use this skill for downstream user projects that merely depend on @clickhouse/client or @clickhouse/client-web; it is specific to contributing to the ClickHouse/clickhouse-js repo itself.
clickhouse-js-node-rowbinary
clickhouse/clickhouse-js
Generate TypeScript/JavaScript code that reads/decodes AND writes/encodes ClickHouse RowBinary streams for the ClickHouse HTTP server. Use this skill whenever a user wants to parse or produce RowBinary, RowBinaryWithNames, or RowBinaryWithNamesAndTypes. Node.js only, doesn't cover browsers.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.