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

voxelkloud

v0.5.2

Published

The voxelkloud CLI — inspect, diagnose, serve and convert point clouds. Also the signpost to the scoped browser packages.

Readme

voxelkloud

The command-line tool. Also the signpost to the browser packages.

npx voxelkloud@latest inspect https://example.com/clouds/autzen/ --deep

No toolchain, no build step: this package carries a small launcher, and npm installs the one prebuilt binary that matches your platform.

What it does

voxelkloud inspect <target>    # what is this? format, size, attributes, CRS, hierarchy
voxelkloud doctor  <url>       # why does this deployment feel broken?
voxelkloud serve   [dir]       # a static server with byte ranges and CORS
voxelkloud convert <inputs...> # LAS/LAZ in; Potree v2, COPC or EPT out

inspect reads a directory, a manifest, a .las/.laz/.copc.laz or a URL, and prints the same shape for all of them.

doctor is the one to reach for when a cloud loads locally and not in production. It asks the questions the formats actually depend on — does the server answer 206, does the browser get to read Content-Range, is something gzipping a file that is already compressed — and says what to change. It works against a Potree deployment you already have, and exits non-zero when something is broken, so it fits in CI:

- uses: voxelkloud/voxelkloud@v1
  with:
    run: doctor https://cdn.example.com/clouds/site-a/ --deep

Other ways to install

npm install -g voxelkloud
cargo install voxelkloud-cli
brew install voxelkloud/tap/voxelkloud

Or a static binary from the releases.

The browser packages

import "voxelkloud" throws on purpose — there is no module here. The renderer ships as scoped packages, so you take only the part you need.

| You want | Install | | --- | --- | | A React component | npm install @voxelkloud/react three | | A Vue 3 component | npm install @voxelkloud/vue three | | The renderer, no framework | npm install @voxelkloud/view @voxelkloud/loader three | | To read cloud data, not draw it | npm install @voxelkloud/loader |

import { PointCloudViewer } from "@voxelkloud/react";

<PointCloudViewer
  url="https://example.com/clouds/autzen/"
  style={{ position: "absolute", inset: 0 }}
/>;

Full documentation: https://github.com/voxelkloud/voxelkloud

MIT.