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

@sf-agentscript/lsp-browser

v2.2.31

Published

Browser LSP server for AgentScript — runs in a web worker with WASM parser

Downloads

39

Readme

@agentscript/lsp-browser

Browser LSP server for AgentScript. Runs in a web worker with the TypeScript parser — the browser counterpart to @agentscript/lsp-server.

How It Works

This package creates a browser LSP connection (via BrowserMessageReader/BrowserMessageWriter) and calls setupServer() from @agentscript/lsp with:

  • TypeScript parser (default) — pure JS, no WASM initialization required
  • Tree-sitter parser (optional) — when built with pnpm build:tree-sitter, init() loads WASM binaries in the onBeforeInitialize hook before the first parse
  • Query executor — CST-walk highlighter for semantic token highlighting
  • Dialect registry — ships with agentforce and agentscript dialects
  • Deferred initialization — parser is loaded inside the onBeforeInitialize hook, so the connection is set up synchronously before any client messages arrive

All LSP features (diagnostics, hover, completion, go-to-definition, references, rename, symbols, code actions, semantic tokens) are provided by @agentscript/lsp — this package only wires up the browser-specific bindings.

See @agentscript/lsp README for the full architecture and feature list.

Installation

pnpm add @agentscript/lsp-browser

Usage

Import this module from a web worker. The module self-starts: it creates a connection on the worker's message port, initializes the parser on first client handshake, and begins listening.

// worker.ts
import '@agentscript/lsp-browser';

Then, from your main thread (e.g., a Monaco editor integration):

const worker = new Worker(new URL('./worker.ts', import.meta.url), {
  type: 'module',
});
// Connect the worker to your LSP client (e.g., monaco-languageclient)

Adding a Dialect

Register your dialect in packages/lsp/src/dialect-registry.ts (the shared registry in @agentscript/lsp):

import { mydialect } from '@agentscript/mydialect-dialect';

export const defaultDialects: DialectConfig[] = [
  agentforceDialect,
  agentscriptDialect,
  mydialect, // add here
];

See the Adding a New Dialect guide for full instructions.

Development

pnpm build     # Build (ESM + browser bundle + declarations)
pnpm dev       # Watch mode
pnpm typecheck # Type-check

License

MIT