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

@elumixor/asset-viewer

v2.0.4

Published

A simple asset viewer for PixiJS and Three.js

Readme

Asset Viewer

Build Latest NPM version

A simple asset viewer for PixiJS and Three.js projects.

Usage

npm install --save-dev @elumixor/asset-viewer

# Start viewer pointing directly to a directory containing .glb/.gltf/.png/.jpg/.jpeg/.webp files
npx asset-viewer ./path/to/assets

# Custom port
npx asset-viewer ./path/to/assets --port 6001

# Auto-open in browser
npx asset-viewer ./path/to/assets --open

Open your browser at the printed URL (defaults to http://localhost:5735).

The provided path can be either:

  1. A folder that directly contains model/texture files (served under /assets).
  2. A project root that contains public/assets (that subfolder will be used).

Command line options:

Usage: asset-viewer [options] <path>
    -p, --port <number>  Port to run the server on (default: 5735)
    -o, --open           Open default browser pointing to server root after start
    -V, --version        Output version
    -h, --help           Display help

Notes:

  • Client is a React + Vite bundle (Three.js + GLTF previews).
  • Three.js is resolved from local node_modules with standard ESM import (no inline import map).

Development (Hot Reload)

Single command dev environment with Bun hot server + Vite HMR client:

bun run dev -- ./test/assets --port 5735

Details:

  1. Starts the asset viewer server via bun run --hot src/asset-viewer-server.ts ... (automatic restart on changes).
  2. Starts vite dev for the React client (port 5173 by default) and proxies /api + /assets to the Bun server port.
  3. Pass any normal CLI arguments to the server after -- (path, --port, etc.).

Open the Vite dev URL it prints (e.g. http://localhost:5173) during development. For a production-like bundle, run bun run build then execute the generated CLI (npx asset-viewer ...).