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

voxelsrv-protocol

v0.3.4

Published

For client, see [VoxelSrv/voxelsrv](https://github.com/VoxelSrv/voxelsrv) For server, see [VoxelSrv/voxelsrv-server](https://github.com/VoxelSrv/voxelsrv-server)

Readme

For client, see VoxelSrv/voxelsrv For server, see VoxelSrv/voxelsrv-server

VoxelSrv is using Protocol Buffers with additional byte (ID) at the beginning - [id byte, ...serialized protocol buffer output]. ID is based on position of message in definition file (so for client, LoginResponse = 0. Ping = 1...). IDmap can be also found in idmap folder as a JSON array. Data itself is send via WebSocket (ws:// for unencrypted and wss:// for encrypted).

If you need files for other languages than provided, you can copy proto folder and use any protocol buffer 3 implementation.

Server.* and client.* files are most likely ones you need. Proxy-* is only used for connecting to non-websocket based servers with main (or any other) proxy. Mostly used for mc0.30c support

If you want to use it, you should check: