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

wow-wmo-web

v0.7.2

Published

Read World of Warcraft WMO world model files in the browser and Node.js (WebAssembly bindings for wow-wmo)

Readme

wow-wmo-web

npm

Read and write World of Warcraft WMO world model files in the browser and Node.js — WebAssembly bindings for the wow-wmo Rust crate. A WMO is one root file plus N group files (name.wmo, name_000.wmo, …). Everything happens in memory.

Group geometry (the heavy part) is loaded lazily through a resolver callback and exposed as typed arrays.

Getting the package

Install from npm (recommended for JS/TS):

npm install wow-wmo-web

Or download wow-wmo-web-<version>-web.tar.gz from the GitHub releases and unpack it (tar xzf ... creates ./pkg/), or build it yourself:

rustup target add wasm32-unknown-unknown
cargo install wasm-bindgen-cli

cargo build --release -p wow-wmo-web --target wasm32-unknown-unknown
wasm-bindgen --target web --out-dir wrappers/wow-wmo-web/pkg \
  target/wasm32-unknown-unknown/release/wow_wmo_web.wasm

Usage

import init, { WmoFile } from "wow-wmo-web";
// If you downloaded the tarball or built locally, use:
// import init, { WmoFile } from "./pkg/wow_wmo_web.js";
await init();

// Monolithic root-only (group files not loaded)
const wmo = new WmoFile(new Uint8Array(await file.arrayBuffer()));

wmo.summary();
// {
//   version, groupCount, loadedGroupCount,
//   textures: [...], materialCount, portalCount,
//   lightCount, doodadDefCount, doodadSetCount,
//   boundingBoxMin, boundingBoxMax,
//   skybox, groups: [{index, name, flags, loaded, vertexCount, triangleCount}, ...]
// }

wmo.addTexture("tileset/dungeon.blp");
const rootBytes = wmo.exportRoot();          // Uint8Array

// Load with groups (Cataclysm+ or legacy multi-file)
const wmo2 = WmoFile.loadWithGroups("dungeon.wmo", rootBytes, (name) =>
  archive.hasFile(name) ? archive.readFile(name) : undefined,
);
const verts = wmo2.groupVertices(0);        // Float32Array (x,y,z interleaved)
const normals = wmo2.groupNormals(0);       // Float32Array
const uvs = wmo2.groupTexCoords(0);         // Float32Array (u,v interleaved)
const indices = wmo2.groupIndices(0);       // Uint16Array

// Creating from scratch
const fresh = WmoFile.create("wotlk");
fresh.addTexture("tileset/dungeon.blp");

Notes

  • loadWithGroups derives group filenames from the root name using the conventional <stem>_000.wmo, <stem>_001.wmo, … pattern.
  • Group files are parsed read-only; only the root file is writable.
  • The resolver is called for every expected group file. Returning undefined/null for a missing file is an error (unlike optional split ADT companions, groups are required when listed by the root).