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

kythe-languageserver

v0.1.1

Published

A language server for Kythe

Downloads

15

Readme

Building

Be sure to run npm install from the languageserver directory in order to fetch dependencies.

We also need to compile the appropriate protos so be sure to run:

npm run proto

This is only required on first setup and when the protos change.

To build the server, run:

npm run compile

or

npm run watch

Testing

In order to test the server, run:

npm run test

If you wish to run a watch build on tests, run:

npm run watch_test

Running

The server communicates over the (Language Server Protocol](https://github.com/Microsoft/language-server-protocol) (specifically v2).

The server, by default, makes requests to localhost:8080 which should be running an HTTP interface for the Kythe xref service.

A .kythe-settings.json file is required in the root of your project. See Configuration for more details.

STDIO communication

node dist/src/bin/kythe-languageserver.js --stdio

Socket communication

node dist/src/bin/kythe-languageserver.js --pipe=/tmp/socket.sock

Node IPC

node dist/src/bin/kythe-languageserver.js --ipc

Configuration

The server looks for a kythe-settings.json file in the root of the workspace. See this example config file containing all possible options:

{
    "mappings": [{
        "local": ":file*",
        "vname": {
            "path": "kythe.io/:file*",
            "corpus": "kythe"
        }
    }],

    "xrefs": {
        "host": "localhost",
        "port": 8080
    }
}

Editor specific instructions

Neovim

If you're using LanguageClient-neovim, it sets its workspace root as the directory containing the first file opened with the proper extension. The most expeditious workaround is to just open a file at the top level first then open anything else. There is an open issue about this: https://github.com/autozimu/LanguageClient-neovim/issues/70