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

@thai-kit/props

v0.4.3

Published

Game-ready Thai street props as procedural Three.js source: a vibe3d pack of 180 factories that build a THREE.Group in code.

Readme

@thai-kit/props

A vibe3d pack of 180 game-ready Thai street props, shipped as procedural Three.js source rather than as GLB files.

Every prop is a factory that builds a THREE.Group in code. vibe3d add installs the TypeScript into your app, shadcn-style, and from then on it is yours to edit.

npx vibe3d add @thai-kit/props        # the whole kit
npx vibe3d add @thai-kit/oil-drum     # one prop

Each installed prop is four files:

  • createObjectModel.ts — the factory, byte-identical to the one in the thaikit repo.
  • model.ts — the vibe3d entry point: createModel(options) and createPreview().
  • thaikit.json — thaikit's full asset record: declared and measured metres, pivot and placement rules, physics (enabled, massKg), destruction groups, the four scene-budget ceilings, the named pivots and sockets the factory exposes, and the generation review.
  • colliders.json — the physics compound: a handful of boxes and cylinders in root-local metres (scale is half-extents), with the ray-cast self-check that measured it.
import { createModel } from './models/oil-drum/model';

scene.add(createModel({ castShadow: true, textureSize: 512 }));

Requirements

three >= 0.185.0, as a peer dependency. The factories import bare three; your app supplies it, and there must be exactly one copy — a second instance means the factory's Mesh is not the renderer's Mesh and nothing draws.

Extra data the pack carries as files

A vibe3d pack can ship any file alongside an item's model.ts, and thaikit uses that to carry the game-side data for every prop: thaikit.json (mass, physics flags, placement rules, pivots, destruction groups, render budgets and the review score) and colliders.json (a hand-checked walkable shell of boxes and cylinders, in root-local metres). vibe3d add installs both beside the factory like any other file, so a game can read a prop's mass, its collider compound or its budget straight from the install with no extra tooling. The source of truth is the tree at packages/props/src/models/ in the thaikit repo; this registry is built from it.

Licence

MIT. The geometry is fully synthetic — no scanned or scraped meshes.