What is this?
This is the home of the Language Server Protocol (LSP), Microsoft's specification that defines a common protocol for language servers — the components editors and IDEs talk to for language features like autocomplete.
This is the home of the Language Server Protocol (LSP), Microsoft's specification that defines a common protocol for language servers — the components editors and IDEs talk to for language features like autocomplete.Is this an app or library I install, or something else?Neither — it is a specification repository. It hosts the protocol documents, not a runtime: there is no package to install, no build scripts and no dependencies in the repo.
Neither — it is a specification repository. It hosts the protocol documents, not a runtime: there is no package to install, no build scripts and no dependencies in the repo.How do I start using it in my own tool?Read the specification at https://microsoft.github.io/language-server-protocol/ and implement the defined messages in your language server or editor client. Nothing needs to be installed to work with the spec itself.
Read the specification at https://microsoft.github.io/language-server-protocol/ and implement the defined messages in your language server or editor client. Nothing needs to be installed to work with the spec itself.If I follow the spec, will my editor just work — what's the catch?The spec only defines the protocol, it ships no code that runs. You still have to implement both sides — the language server and the editor client — or reuse an existing implementation library.
The spec only defines the protocol, it ships no code that runs. You still have to implement both sides — the language server and the editor client — or reuse an existing implementation library.Is this for end users or for people building editors?Primarily for tool builders: authors of editors, IDEs and language servers who need their products to interoperate. End users benefit indirectly when their editor speaks the protocol.
Primarily for tool builders: authors of editors, IDEs and language servers who need their products to interoperate. End users benefit indirectly when their editor speaks the protocol.How established is LSP among editors and tools?Very: the repository has been public since September 2015, is maintained under the Microsoft org and has around 13,000 stars. It is widely treated as the standard way for editors to talk to language servers.
Very: the repository has been public since September 2015, is maintained under the Microsoft org and has around 13,000 stars. It is widely treated as the standard way for editors to talk to language servers.Why does a shared protocol matter?Because a language server can be written once and reused by any editor that speaks the protocol, instead of every tool integrating every language separately. That is the whole point of the common protocol in the description.
Because a language server can be written once and reused by any editor that speaks the protocol, instead of every tool integrating every language separately. That is the whole point of the common protocol in the description.Do I need to be a TypeScript developer to use this?No. The repo is labeled TypeScript, but it is mainly specification documents. An LSP implementation can be written in any language — the protocol, not the code, is the product.
No. The repo is labeled TypeScript, but it is mainly specification documents. An LSP implementation can be written in any language — the protocol, not the code, is the product.What are similar projects?rust-analyzer, monaco-editor, ale, rfcs, toast, htn_planner, dsh-std, spec
rust-analyzer, monaco-editor, ale, rfcs, toast, htn_planner, dsh-std, specWhich topics is it in?language-server-protocol, standards, autocomplete, lsp, specification, protocol, ide, microsoft, editor, json, documentation, api
language-server-protocol, standards, autocomplete, lsp, specification, protocol, ide, microsoft, editor, json, documentation, api