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

openjph-wasm

v0.1.0

Published

WebAssembly build of OpenJPH (HTJ2K / JPEG 2000 Part 15) with full multi-component encode and decode.

Readme

openjph-wasm

A WebAssembly build of OpenJPH (HTJ2K / JPEG 2000 Part 15) exposing both encode and decode, with full multi-component support — including independent components, which is what volumetric (z-as-components) imagery needs.

Why this exists

The widely-used @cornerstonejs/codec-openjph npm package is a frozen wrapper (~2 years stale at the time of writing) that cannot round-trip independent multi-component data: it silently keeps component 0 and replicates it across all output components, losing planes 1..N. That is a limitation of that wrapper, not of OpenJPH — current OpenJPH (0.30.x, very actively developed) decodes multi-component data correctly.

openjph-wasm builds OpenJPH's current source itself, adds an encode wrapper, and exposes a small typed API so volumetric / multi-plane HTJ2K chunks can be encoded and decoded faithfully.

Install / build

OpenJPH is vendored as a git submodule and compiled with the official emscripten/emsdk Docker image (no local emsdk needed):

git submodule update --init --recursive
npm install
npm run build          # builds the wasm (Docker) then the TS
npm test               # round-trips single- and multi-component data

Usage

import { encode, decode } from "openjph-wasm";

// `data` is planar, component-major: data[(c*height + y)*width + x]
const codestream = await encode({ data, width, height, components, reversible: true });

const img = await decode(codestream);
// img.components, img.width, img.height, img.bitDepth, img.isSigned
// img.data — planar, component-major typed array

components map naturally to z-planes of a volumetric chunk. Lossless uses the reversible 5/3 transform; pass { reversible: false, quality } for irreversible 9/7.

License

BSD-2-Clause, matching OpenJPH. See LICENSE.