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

@threeops/optimize

v0.9.0

Published

Analyze and optimize glTF models in place: KTX2 or WebP textures, outlier texture caps, meshopt geometry. Idempotent, for asset pipelines.

Readme

@threeops/optimize

The part of ThreeOps that runs inside a customer's project: analyze and optimize glTF models in place, as a step in their asset pipeline. Small on purpose: no browser, no CLI framework.

threeops-optimize public/content/models --cap 2048
  • Textures: KTX2, with KTX-Software 4.3+ (ktx): ETC1S for colour, UASTC for normal maps (at half the cap, 512 px minimum), so they stay compressed in GPU memory. ktx is found on PATH, in the standard install folders, or at THREEOPS_KTX. Without it, threeops-optimize stops (exit 2) instead of quietly making WebP, which would use 4-8x more GPU memory. --allow-webp makes WebP on purpose; KTX2 files already made are never downgraded by a machine without KTX.
  • Texture outliers: a file whose textures are much larger than the rest of its folder gets that folder's typical size (e.g. one 2048 px gun among 512 px weapons).
  • Geometry and the rest: dedup, instancing, prune, weld, animation resampling, meshopt compression.
  • Idempotent: a .threeops-cache.json manifest records each output's hash and settings, so reruns skip files it produced. Changing --cap re-runs them.
  • Never worse: if the optimized file isn't lighter on the GPU or the wire, the original is kept.

Options: --cap <px> (default 2048), --images (also resize and re-encode images, same format and name), --image-cap <px>, --allow-webp, --no-ktx2, --quiet.

Guard before builds: threeops-optimize --check <dir> exits 1 unless every model under <dir> is an unchanged output of threeops-optimize with KTX2 textures. threeops fix puts it in the project's prebuild script, so npm run build (and every deploy that builds) refuses an export that didn't finish optimizing.

As a library: import { optimizeDir, optimizeFile, analyzeFile, findSceneIssues, BUDGETS } from '@threeops/optimize'. The threeops CLI (packages/cli) uses it for audits, and threeops fix vendors it into projects as vendor/threeops-optimize-<version>.tgz.

KTX2 encoding calls ktx create directly with the same settings as glTF-Transform's toktx() (verified byte-identical on real models), which keeps this package at ~50 dependencies instead of ~200.