Package Version Server

Why it's ranked here

This is a focused editor utility with useful detail beyond a simple version lookup. Structured parsing avoids treating arbitrary JSON keys as packages, while caching limits repeated registry requests. The narrow scope is clear, but network dependence and an evidently stale parser test reduce confidence in reliability.

What's good

It recognizes regular, development, peer, optional, and bundled dependency sections. Hover output combines package identity, description, latest version, relative publication time, and homepage. Version completion strips common range operators, filters against the typed text, sorts newer semantic versions first, and reports unparseable registry entries through editor warnings.

Tradeoffs

The server relies on npm registry responses and converts fetch or parsing failures into generic internal errors. Its cache lasts only 30 seconds, so longer sessions can repeat network requests. It synchronizes complete document contents rather than incremental edits. The included parser test no longer matches the parser interface or return type.

How to use it well

Use it when you frequently inspect or edit npm dependency ranges and want registry context without leaving the editor. It fits editors that can launch a standard language server over input and output streams. It does not install packages, resolve dependency conflicts, audit security, or manage lockfiles.

Observed

License

MIT

Primary language

Rust, using the 2021 edition

Interface

Language Server Protocol over standard input and standard output

Registry

Reads package metadata from the npm registry HTTP endpoint

Release packaging

GitHub release workflow publishes compressed binary assets

Platform support

Release targets cover x86-64 and ARM64 on Linux, macOS, and Windows

Parsing

Tree-sitter JSON restricts matches to recognized dependency sections