npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@vue-html-bridge/language-server

v0.1.7

Published

LSP server that publishes vue-html-bridge diagnostics and hover.

Readme

@vue-html-bridge/language-server

A standalone Language Server Protocol server for vue-html-bridge: publishes diagnostics and hover information for .vue files, backed by @vue-html-bridge/analyzer and the built-in @vue-html-bridge/adapter-markuplint adapter (plus any external adapters your workspace's settings enable).

This package ships standalone — a stdio binary plus a library entry point — with no bundled editor client in this release (ADR-0009). Point any LSP-capable editor's generic "custom language server" configuration at the binary below.

Installation

npm install --global @vue-html-bridge/language-server

or as a project dependency your editor extension launches directly.

Running it

vue-html-bridge-language-server --stdio

The server speaks LSP over stdio. It negotiates UTF-16 position encoding by default (falling back to whatever the client declares if UTF-16 isn't offered), supports incremental text sync, and publishes diagnostics on didOpen/didChange/didSave with a 200 ms debounce for didChange.

Configuration

Settings are the shared schema from @vue-html-bridge/settings — the same fields the CLI accepts as flags — resolved from, in precedence order: workspace/configuration, the discovered .vue-html-bridge.json / package.json#vueHtmlBridge, then package defaults. Pass initializationOptions: { workspaceTrusted, settings } at initialize to seed trust and a settings fallback for clients that don't support workspace/configuration.

Trust (language-server.md §4.2): a workspace must be explicitly marked trusted (via initializationOptions.workspaceTrusted or settings) before the built-in Markuplint adapter will read the workspace's own config/plugins, or before any external adapter loads at all. An untrusted workspace still analyzes with the bundled, safe default Markuplint configuration — analysis never stops, only workspace-code execution is gated.

Multi-root: each workspace folder gets its own settings, adapter sessions, and analysis cache; a file outside every folder gets a restricted, untrusted, per-directory session of its own.

Programmatic usage

import { startLanguageServer } from "@vue-html-bridge/language-server";
import { createConnection } from "vscode-languageserver/node";

const handle = startLanguageServer({
  connection: createConnection(process.stdin, process.stdout),
});
// handle.dispose() on shutdown

See docs/design/packages/language-server.md for the full protocol surface, settings precedence, and trust model.