444eb0d1ae
|
||
|---|---|---|
| .github | ||
| public | ||
| scripts | ||
| src | ||
| tests | ||
| .gitignore | ||
| .postcssrc.js | ||
| .prettierrc | ||
| .travis.yml | ||
| LICENSE | ||
| README.md | ||
| cypress.json | ||
| jest.config.js | ||
| package.json | ||
| tsconfig.json | ||
| tslint.json | ||
| vue.config.js | ||
| yarn.lock | ||
README.md
Language Server Protocol Inspector
Try it at https://microsoft.github.io/language-server-protocol/inspector/.
Motivation
When you are using vscode-languageserver-node to develop a language server, it's possible to specify a setting "[langId]".trace.server: "verbose" to make the Language Client log the LSP communication. This log is useful for developing and testing the Language Server, but the log can be lengthy — 5 seconds of usage might generate 5000 lines LSP log. This makes it hard to gain insight from the logs.
This inspector visualizes the logs to make it easy to understand the communication between the Language Client / Server. It also lets you filter down the logs by search query or language features, so you can quickly identify the logs you are interested in.
Usage
- A log file (log from html Language Server) is loaded by default.
- Click each LSP item to expand its parameters.
- Type a query into the search bar to filter the logs.
- Select a language feature area to filter the logs.
- Collect your own logs and inspect them! For example:
- Set
css.trace.server: "verbose"in VS Code. - Open a CSS file.
- Copy everything inside
CSS Language Serverchannel into a log filecss.log. - Load it from the web app.
- Set
- You can try it on real-world logs file at
/tests/unit/logParser/fixture.
Running & Developing
yarnyarn serve
License
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT License.