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/wasm-core

v0.5.1

Published

Rust/wasm kernels for voxelkloud's LOD scheduler: frustum extraction, AABB classification and screen-space-error priority over the wasm linear memory.

Readme

@voxelkloud/wasm-core

Rust LOD kernels for voxelkloud, as raw wasm over linear memory. 3,603 bytes, 1,467 gzipped.

npm install @voxelkloud/wasm-core
import { loadWasmKernels } from "@voxelkloud/wasm-core";
import { selectVisible } from "@voxelkloud/view/lod";

const kernels = await loadWasmKernels(wasmBytes);
selectVisible(tree, cam, options, scratch, out, kernels);

No wasm-bindgen. These are pure f64 functions, so JS reads and writes fixed offsets through Float64Array views and the module needs no generated glue.

OPT-IN, and not wired in by default. @voxelkloud/view/lod declares the kernel surface structurally rather than importing it, so the scheduler keeps its zero-dependency import graph and the TypeScript path stays the differential-test oracle.

MEASURED, warm, against that oracle: 1.1x to 1.45x on selection, which is about 0.6 ms of a 16.6 ms frame at the most extreme setting. At the shipped defaults selection costs 0.1-0.5 ms, where this is irrelevant. Reach for it only after measuring that selection is your bottleneck.

Building from source needs cargo and rustup target add wasm32-unknown-unknown.

MIT.