vscode-debugadapter-node
language-server-protocol

vscode-debugadapter-node | language-server-protocol | |
---|---|---|
1 | 132 | |
288 | 12,101 | |
1.4% | 1.1% | |
4.4 | 8.3 | |
6 months ago | 11 days ago | |
TypeScript | HTML | |
GNU General Public License v3.0 or later | Creative Commons Attribution 4.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vscode-debugadapter-node
-
LSP could have been better
https://github.com/microsoft/vscode-debugadapter-node/issues...
language-server-protocol
-
How to Build a stdio MCP Server in Rust
MCP servers use two transport mechanisms: stdio (standard input/output) and SSE (Server-Sent Events). The stdio transport communicates through standard input/output, similar to LSP (Language Server Protocol) servers, making it fast and efficient for local use. These servers are installed locally and have full access to your machine, for example they can interact with the file system, execute shell commands, access databases, or interact with any local services.
-
Securing MCP: Applying Lessons Learned from the Language Server Protocol
I was deeply involved with the Language Server Protocol (LSP) from its earliest days at Red Hat, one of the instrumental organizations in driving LSP adoption. During that time, I contributed to several key implementations, including the second-ever language server—the Java Language Server—and the widely adopted YAML Language Server. These projects became benchmarks for reliability and widespread adoption in developer communities.
- Show HN: Mcp-Agent – Build Effective Agents with Model Context Protocol
- Show HN: Emcee – connect agents to APIs (via MCP)
-
The Language Server Protocol - Building DBChat (Part 5)
This is my understanding of LSP. The official definition of LSP is as follows from Microsoft:
-
Brakeman LSP Support
Language Server Protocol (LSP) is a standard for communication between code editors and code-related tools. It enables tools to hook into standard events for code review, code completion, formatting, etc.
-
LSP: The Good, the Bad, and the Ugly
I've implemented a LSP server (for Slint - https://slint.dev) and I agree with this article.
The paradox is that it was meant to avoid to write language support for each editor. Yet, if you want to support vscode you must create a specific extension for it and can't just have a language client.
The article mention the configuration problem, but I'd add the problem that Microsoft refuses to specify a way for the server to tell the client what are the config options so that the client can show some kind UI showing the possible configuration options with a description of what they do. https://github.com/microsoft/language-server-protocol/issues...
-
Setup your own Standalone/Local Stellar Blockchain to test different Smart Contracts & dApps
Which is an implementation of Language Server Protocol for Rust programming language. It provide a lot of useful features for your development in Rust, such as code completion, syntax highlighting, inlay hints, etc. You can checkout the manual of rust analyzer to know more about it.
- LSP: Support announcing to the server whether the user trusts the project
-
Integrating the ruff language server
From the LSP website:
What are some alternatives?
iceberg - Iceberg is the main toolset for handling VCS in Pharo.
tree-sitter - An incremental parsing system for programming tools
python-lsp-server - Fork of the python-language-server project, maintained by the Spyder IDE team and the community
intellij-lsp-server - Exposes IntelliJ IDEA features through the Language Server Protocol.
rust-analyzer - A Rust compiler front-end for IDEs
tree-sitter-org - Org grammar for tree-sitter
