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/format-potree

v0.5.1

Published

Potree v2 driver for voxelkloud: metadata.json/hierarchy.bin/octree.bin over HTTP Range requests.

Readme

@voxelkloud/format-potree

The Potree v2 driver for voxelkloud — one format among several, not the shape of the library.

npm install @voxelkloud/format-potree

Most applications never install this directly: @voxelkloud/loader registers it on the first load, so pointing the loader at a Potree directory just works. Install it by name when you want the driver's own fields — source.metadata, source.isBrotli, the decoded point records — or when you are pinning the format on purpose.

What is actually Potree-specific

That distinction is the reason this package exists. The vocabulary every driver shares — bounding boxes, attributes, transport, warnings, the source and tree contracts, octree subdivision and Morton order — lives in @voxelkloud/core. What is here is what genuinely belongs to this format:

  • the metadata.json schema, including hierarchy.firstChunkSize and encoding
  • the 22-byte hierarchy.bin node record, and the proxy-chunk paging over it
  • r047 node naming — EPT keys a node D-X-Y-Z, COPC keys it level-x-y-z
  • the DEFAULT interleaved stride and the BROTLI planar 47 B/pt block, with morton-coded positions and colour

Using it directly

import { loadPotreeSource, loadHierarchy } from "@voxelkloud/format-potree";

const source = await loadPotreeSource("https://example.com/clouds/autzen/");
source.metadata.points;      // 10653336 — the driver's own field
source.pointCount;           // 10653336 — the neutral one
source.bytesPerPoint;        // 35
source.warnings;             // tolerated anomalies, never thrown

const tree = await loadHierarchy(source);

potreeFormat is the same driver as a registry entry, for formats.register(...).

BROTLI

No browser exposes a brotli decoder to JS, so a BROTLI-encoded cloud needs one supplied. Resolution is tiered — injected, then Node's zlib, then DecompressionStream — and the vendored reference decoder is opt-in behind the @voxelkloud/format-potree/brotli subpath and never auto-imported.

MIT. This package vendors the Brotli Authors' reference decoder; see THIRD-PARTY-NOTICES.md.