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

@holoscript/lsp

v6.2.0

Published

Language Server Protocol implementation for HoloScript

Readme

@holoscript/lsp

Language Server Protocol implementation for HoloScript.

Installation

npm install @holoscript/lsp

Features

  • 🎯 Autocomplete - Intelligent code completion
  • 🔍 Hover - Documentation on hover
  • 📍 Go to Definition - Navigate to declarations
  • 🔎 Find References - Find all usages
  • ✏️ Rename - Safe symbol renaming
  • 🔧 Code Actions - Quick fixes and refactors
  • 🎨 Semantic Highlighting - Rich syntax coloring
  • ⚠️ Diagnostics - Real-time error reporting

Usage

As a Server

import { startServer } from '@holoscript/lsp';

startServer({
  connection: createConnection(),
  documents: new TextDocuments(TextDocument),
});

With VS Code

The LSP is bundled with @holoscript/vscode.

With Neovim

require('lspconfig').holoscript.setup({
  cmd = { 'holoscript-lsp', '--stdio' },
})

AI Autocomplete

Enable AI-powered suggestions:

import { createAutocomplete } from '@holoscript/lsp';

const autocomplete = createAutocomplete({
  provider: 'copilot',
  context: 'vr-game',
});

Package boundary & release posture

@holoscript/lsp is the Language Server Protocol backend for HoloScript, built for external editor integrations (VS Code, Neovim, and any other agent framework or agent-family tool that speaks LSP) rather than for one specific bundled editor. The server does not ship an editor — the caller owns the connection and TextDocuments transport it is started with, and any AI-autocomplete backend (createAutocomplete({ provider, context })) is caller-owned: you point it at your own provider id and supply any provider credentials through your own environment variables, never a package default.

The package does not ship founder-local configuration, private workspace paths, or a bundled AI backend. Workspace root, provider keys, and connection transport are all supplied by the operator at start time, not baked into the package.

Operability: the server exposes standard LSP diagnostics/validation over the protocol, so a host editor or CI harness gets the same doctor-style health signal any LSP client already knows how to consume.

Release posture: v0-preview. Known limitations — AI-autocomplete providers beyond the documented example are unverified against this package, and the debug-adapter surface is still evolving. Pin a version in consuming projects; rollback is a plain npm install @holoscript/lsp@<previous-version>.

License

MIT