8000 GitHub - Nimblesite/lspkit · GitHub
[go: up one dir, main page]

Skip to content
NimblesitePublic

About

No description, website, or topics provided.

Resources

Stars

2 stars

Watchers

0 watching

Forks

Latest commit

 

History

31 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

lspkit logo: charcoal and vermilion code braces

lspkit — The foundation for any language's tooling. One Rust engine feeds LSP, MCP and the profiler.

Docs  ·  Getting started  ·  Examples  ·  Journal

lspkit on crates.io lspkit-server on crates.io lsp-profiler on crates.io @nimblesite/lsp-profiler-ui on npm MIT license

Rust crates for building language servers. Your analysis runs once, in one engine, and an LSP server, an MCP server and a CPU and memory profiler all read from it.

cargo add lspkit lspkit-server

What's in the box

CrateWhat it gives you
lspkitEngineApi and its types, plus config, vfs, sidecar and, behind treesitter, tree-sitter helpers.
lspkit-serverJSON-RPC LSP scaffolding on lsp-types: capabilities, dispatch, diagnostics, progress, cancellation, live file watching and, behind mcp, the MCP adapter.
lsp-profilerLanguage-neutral CPU and memory profiler: hotspots, flame graphs, speedscope/V8 export, heap snapshots, leak scoring. Spec.
lsp-profiler-dotnetThe profiler's .NET runtime, using EventPipe.
@nimblesite/lsp-profiler-uiThe VS Code profiler UI: processes, heat map, flame graph, memory dashboard, retention graph, plus Debug Adapter Protocol test glue.

Built with lspkit

Two language servers ship the lspkit profiler in VS Code today. Click a picture to watch it run.

Watch: profiling a C# app in VS Code with SharpLsp

SharpLsp · C# and F#
Attach to any running .NET process. Hot lines light up in your code and leak suspects are ranked live. Watch the profiler ▶

Watch: profiling Osprey in VS Code, CPU, memory and leaks

Osprey · native functional language
Run and profile the open file, read the flame graph, attach to a running program and check for leaks. Watch the tutorial ▶

SharpLsp: CheckoutPipeline.cs with inline heat bars on the hottest methods Osprey: busy.osp with inline heat bars on collatz, longest and fib
SharpLsp: suspected leaks ranked HIGH with an inline leak marker in the source Osprey Profiler panel with sample counts above a flame graph

One engine, two surfaces

EngineApi is the single boundary between your analysis and the protocols. The LSP backend and the MCP server consume the same engine, so live analysis state is computed once and served both ways. Every report carries a generation number, so clients know which workspace state produced an answer. lsp-profiler-python is parked and unpublished.

Build

make ci      # lint + test + build (full CI simulation)
make test    # fail-fast tests + coverage + threshold
make lint    # cargo clippy -- -D warnings

Spec

Behavior contract: docs/specs/lspkit-spec.md. Execution plans: docs/plans/.

License

MIT — see LICENSE-MIT. © Nimblesite.

About

No description, website, or topics provided.

Resources

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

0