vscode-languageserver-node

The vscode-languageserver-node repository provides several npm modules for building and consuming Language Server Protocol (LSP) implementations in Node.js:

• vscode-languageclient: Used by a VSCode extension to communicate with a language server.
• vscode-languageserver: Used to implement the language server itself using Node.js.
• vscode-languageserver-textdocument: Provides text document implementations for use within an LSP server.
• vscode-languageserver-protocol: Contains the TypeScript definitions for the Language Server Protocol.
• vscode-languageserver-types: Contains the data types used by both the client and the server.
• vscode-jsonrpc: The underlying JSON-RPC message protocol used for communication between the client and server.

The tsconfig-gen tool helps maintain consistent tsconfig.json files in monorepos. Instead of manually managing multiple files, you define a high-level configuration that the generator uses to produce specific configurations.

Key capabilities include:

• Multiple Base Configurations: Extending from several base configs simultaneously.
• Project Dependency Management: Automatically generating proper references based on project dependencies.
• Source Folder Specialization: Generating different compiler configurations for specific source folders within a project (e.g., creating separate configs for common, browser, or node code).
• Lifecycle-based Configurations: Generating distinct compiler settings for different tasks like compile, watch, or publish.

The vscode-languageserver npm module provides the necessary tools to implement a Language Server (LSP) using Node.js as the runtime. This allows you to build language intelligence features (like autocompletion, go-to-definition, and diagnostics) that can be consumed by VS Code and other LSP-compatible editors.

For a comprehensive step-by-step guide on implementation, refer to the official VS Code documentation: Example Language Server.

The vscode-languageclient npm module provides a high-level API for VSCode extensions to integrate with language servers that implement the Language Server Protocol (LSP). It handles the communication lifecycle between the VSCode client and the external language server process.

For a comprehensive implementation guide, refer to the official VSCode documentation: Example Language Server.

The vscode-languageserver-protocol module is a tool-independent implementation of the Language Server Protocol (LSP). It can be used in any Node.js application to implement or consume LSP-compliant communication.

Important Versioning Note: This module versions its releases based on the LSP specification version number. Because the protocol implementation depends on vscode-jsonrpc, breaking changes in the JSON-RPC dependency might not always trigger a major version bump in this module. This is done to maintain alignment between the module's version and the official LSP specification version, avoiding version mismatch confusion.

The vscode-languageserver-textdocument npm module provides a simple text document implementation designed for use within Node.js-based Language Servers (LSP). It allows your server to manage and interact with text documents in a way that is compatible with the Language Server Protocol (LSP) requirements.

For a comprehensive guide on implementing a full language server for VSCode, refer to the official VSCode documentation: https://code.visualstudio.com/docs/extensions/example-language-server

Document selection and filtering have been updated:

• Typed Filters: DocumentFilter and NotebookDocumentFilter are now reified into specific variants like ...FilterLanguage, ...FilterScheme, and ...FilterPattern.
• Glob Patterns: The pattern field now uses GlobPattern, allowing registrations to use RelativePattern. This is gated by TextDocumentFilterClientCapabilities.relativePatternSupport.
• Notebook Filters: Added NotebookDocumentFilterNotebookType, ...Scheme, and ...Pattern.

Markdown support in the protocol has been enhanced:

• Theme Icons: Clients can signal support for icon syntax $(name) via MarkdownClientCapabilities.supportThemeIcons.
• Trusted Markdown: For areas where servers return markdown (hover, signature help, etc.), the isTrusted mechanism has been extended. Servers can provide a list of enabledCommands via the Command type to define which commands are safe to run in a trusted context.

The completion protocol has been updated to allow more granular control over how completion items are merged:

• Item Defaults: CompletionList.itemDefaults is extended with a data field, allowing for per-item default data payloads.
• Merge Strategy: A new CompletionList.applyKind (of type CompletionItemApplyKinds) defines how commitCharacters and data are merged between list defaults and individual items. Supported strategies are Replace and Merge. This is gated by the completionList.applyKindSupport client capability.

The WorkspaceEdit object has been enhanced with the following capabilities:

• Snippet Support: WorkspaceEdit can now carry SnippetTextEdit entries. Clients can check for this via the workspace.workspaceEdit.snippetEditSupport capability.
• Metadata: WorkspaceEditMetadata can be carried in ApplyWorkspaceEditParams.metadata. This is gated by the workspace.workspaceEdit.metadataSupport client capability and currently includes an isRefactoring field.
• Command Tooltips: The Command type now supports a proposed tooltip field.