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

@wasm-idle/lsp

v1.0.0-next.0

Published

Framework-neutral browser LSP hosts for wasm-idle language tools

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

seoriiseorii

Keywords

Readme

@wasm-idle/lsp

Framework-neutral browser language-server hosts for wasm-idle. The npm package contains code only. Language tools and standard-library data must be deployed separately and passed as HTTP(S) URLs.

Installation

@wasm-idle/lsp is an optional editor plugin and is not a dependency of the root wasm-idle package. Installing wasm-idle does not install this package transitively; applications that want editor LSP support must install it explicitly:

pnpm add @wasm-idle/lsp

In particular:

  • TypeScript and JavaScript require typescript.libUrl or javascript.libUrl unless the host supplies libFiles directly.
  • AssemblyScript, SQLite, DuckDB, and Ruby load page-owned runtime modules from their respective moduleUrl option. The modules provide the package glue and default WASM or worker asset URLs. Hosts may still override sql.wasmUrl, sql.duckdbBundles, or ruby.wasmUrl.
  • Python and R load their externally deployed Pyodide and WebR trees from python.baseUrl and r.baseUrl.
  • Clangd and other compiler-backed language servers use their corresponding runtime asset config.

No WASM modules, compressed standard libraries, compiler archives, or worker assets are included in the package tarball.

Pure JavaScript provider engines are optional peer dependencies. Install only the providers used by the application: typescript for TypeScript/JavaScript, graphql for GraphQL, wabt for WAT, and the corresponding VS Code language-service packages for document languages. Importing @wasm-idle/lsp does not load these providers; the selected provider is imported when its language server is initialized. The wasm-idle Pages app keeps @wasm-idle/lsp as a dev dependency and dynamically imports each provider only after LSP is enabled and its language is selected, so provider chunks are not downloaded before they are needed.