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/loader

v0.5.1

Published

Streaming point cloud loader over HTTP Range requests. No three.js and no DOM in its module graph, so it runs in a worker or in Node.

Readme

@voxelkloud/loader

The engine: it identifies which format a URL is, and hands off to that driver. No three and no DOM in its module graph, so it runs in a worker or in Node.

npm install @voxelkloud/loader
import { loadPointCloud } from "@voxelkloud/loader";

const { source, tree, format } = await loadPointCloud(url);
format.id;                 // "potree-v2"
source.pointCount;         // 10653336
source.tightBoundingBox;   // absolute CRS

The returned source satisfies PointCloudSourceBase whichever driver served it. Reach for a driver's own fields only when you have decided to be format-specific.

How it decides

Drivers are ordered by sniffUrl, which is URL shape only and costs nothing. Each candidate then names the document that would identify it — metadata.json for Potree, ept.json for EPT — and those are fetched, once each even when several drivers name the same one, until a driver reports decisive confidence. That document is handed to the winning driver, so identification never costs a duplicate round trip.

A 404 on one candidate is an answer, not a failure: it is how "not this format" presents. When nothing matches, the thrown "unsupported-format" names what was tried and what the server actually served.

Pass format: "potree-v2" to skip sniffing entirely — use it when the format is known and a wrong guess should be an error rather than a fallback.

Drivers

@voxelkloud/format-potree is registered on the first load, so zero-config keeps working. That is a DX decision, not a structural one. The other drivers are separate packages and are NOT registered by default, because each pulls in a wasm LAZ decoder and an app that reads one format should not bundle another's codec to find that out:

import { formats } from "@voxelkloud/loader";
import { copcFormat } from "@voxelkloud/format-copc";
import { eptFormat } from "@voxelkloud/format-ept";

formats.register(copcFormat).register(eptFormat);
formats.unregister("potree-v2");

Once registered, the URL decides. loadPointCloud returns the driver that claimed it, the source, the tree, and openPoints — a factory for the reader that turns a node into vertices, which is the last thing that stays format-specific:

const { format, source, tree, openPoints } = await loadPointCloud(url);
format.id; // "potree-v2" | "copc" | "ept"
view.addCloud(source, tree, openPoints);

MIT.