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

cozyclay

v1.1.0

Published

Browser-based 3D staging studio: block a scene, pose characters, author camera moves and cuts, and preview generated motion.

Readme

CozyClay

CozyClay is a browser-based 3D staging studio built with Three.js and React Three Fiber. Block a scene, pose characters, sequence motion prompts on a timeline, and preview generated motion — in one local workspace that handles like the Unity Editor.

Open the live demo — the studio itself, running in your browser. Nothing to install. It comes seeded with a pre-generated motion clip so you can scrub the timeline, drive the cameras and draw a dolly rail straight away; generating new motion needs a local ARDY machine, so that part is off.

CozyClay browser-based 3D staging studio

Demo

CozyClay motion, staging, and camera workflow

CozyClay can connect to NVIDIA ARDY for motion generation. ARDY is a separate third-party project owned and maintained by NVIDIA; it is not included in this repository, and CozyClay is not affiliated with or endorsed by NVIDIA.

Requirements

  • Node.js 22 or newer
  • npm, or bun
  • A Chromium-based browser
  • Optional: an SSH-accessible NVIDIA machine running ARDY, for motion generation

Quick start

npx cozyclay
# or
bunx cozyclay

That downloads the built studio and opens it at http://127.0.0.1:5180. There is nothing to compile and no dependency tree to install. Useful flags: --port 5200, --no-open, --no-ardy.

Motion generation is off until you point it at a machine that can run it:

CCLAY_ARDY_HOST=user@your-gpu-box npx cozyclay

Everything else, staging through camera work and playback, runs without it.

From a clone

git clone https://github.com/HaD0Yun/CozyClay.git
cd CozyClay
npm install
npm run dev

Open http://127.0.0.1:5180. npm run dev starts the studio together with its local ARDY bridge; npm run dev:ui starts the browser UI alone, without Block Generation.

The bridge listens on loopback only. The environment variables that point it at a remote ARDY machine are documented in tools/ardy/BRIDGE.md.

What you can do

Stage a scene. Create primitives and set pieces, then move, rotate, and scale them with a W/E/R gizmo. Grid snapping is a preference, not a law — hold Ctrl during a drag to invert it. A bird's-eye plan view drives 2D root waypoints for character paths.

Edit like Unity. Right-drag flies the camera (WASD walks, Q/E cranes), middle-drag pans, Alt+drag orbits the selection, left click selects, F frames. The full rule set, its source in Unity's manual, and every deliberate divergence are recorded in docs/unity-reference.md.

Undo anything. Every scene mutation goes through a single history store: one interaction — a drag, a scrub, an inspector edit — is exactly one undo entry. Esc cancels an in-flight drag and restores the pre-drag transform.

Generate motion. Pose characters and export poses, sequence multi-phase motion as Prompt Blocks on a resizable timeline, send them to ARDY, then play the result back with sparse IK correction where the generated motion needs fixing.

Controls

| Input | Action | | --- | --- | | Right-drag | Look around (fly) | | RMB + WASD | Walk while flying | | RMB + Q/E | Crane down / up | | Middle-drag | Pan | | Alt + drag | Orbit the selection | | Scroll | Dolly | | Click | Select; empty space clears | | W / E / R | Move / rotate / scale tool | | Ctrl (during drag) | Invert grid snapping | | Ctrl/Cmd+Z, Ctrl/Cmd+Shift+Z | Undo / redo | | Esc | Cancel the in-flight drag | | End | Drop the selection to the surface | | Ctrl/Cmd+D | Duplicate the selection | | F | Frame the selection |

Validate

| Command | Covers | | --- | --- | | npm run test:history | Undo/redo store and transaction coordinator | | npm run test:scene-objects | Scene-object model | | npm run test:hierarchy | Hierarchy panel model | | npm run test:objects | Gizmo interaction in a real browser — needs npm run dev:ui in another shell | | npm run test:theme / test:appearance / test:layout | UI theme, appearance, layout | | npm run test:lifecycle | Dev-server process lifecycle | | npm run test:ardy | ARDY conversion, playback, and IK pipeline | | npm run build | Production build |

Ad-hoc browser QA, while a dev server is available:

npm run qa:browser -- <qa-script>

Repository hygiene

Generated motion archives, QA output, build output, logs, and local runtime artifacts are not source files and must not be committed. In particular, keep tools/ardy/out/, artifacts/, dist/, .gjc/, and .npz files local.

License

GNU General Public License v3.0 or later — see LICENSE. Third-party projects retain their own licenses and copyright; see THIRD_PARTY_NOTICES.md.