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

vibedgames

v0.2.0

Published

CLI tool for building and deploying games on vibedgames: scaffolding, asset generation, and deploys.

Downloads

277

Readme

vibedgames (CLI)

CLI tool for building and deploying games on vibedgames: scaffolding, asset generation, and deploys.

Install

npm i -g vibedgames

Commands

vg new <slug>                    # scaffold a Phaser 4 + Vite + TS game (official template)
vg new <slug> --engine threejs   # scaffold a Three.js + Vite + TS starter
vg new <slug> --engine react-r3f # scaffold a React + R3F + drei + Vite + TS starter
vg new <slug> --engine none      # minimal Vite + TS + canvas (offline; inline)
vg new <slug> --template owner/repo  # any github degit spec
vg new <slug> --here             # scaffold into the current directory
vg init [dir]         # install Claude Code skills into ./.claude/skills
vg login              # authenticate via browser
vg logout             # clear credentials
vg whoami             # show current user
vg deploy [dir]       # deploy a game directory (reads vibedgames.json or --slug)

vg generate run <model> [params]   # run a generative model (waits for result)
vg generate models [query]        # search/list available models
vg generate schema <model>        # fetch a model's input/output schema
vg generate pricing <model>       # fetch pricing for a model
vg generate status <model> <id>   # check an async request
vg generate upload <file>         # upload an asset, get a URL
vg generate docs <query>          # search generative-model documentation

vg skills install is an alias for vg init. Most commands support --json for machine-readable output.

vg generate calls the generate.forward tRPC proc — the server holds the provider API key, so generation works for any logged-in user with no local keys.

Using with Claude Code

Run vg init in your project to drop the full set of game-building skills (Phaser, Three.js, Aseprite, asset generation, deploy, etc.) into ./.claude/skills/. Claude picks them up automatically on next session.

How deploy works

  1. Walks the directory, hashes files, validates index.html exists
  2. Calls deploy.create API — gets presigned R2 upload URLs
  3. Uploads files to R2 with bounded concurrency
  4. Calls deploy.finalize — game goes live at {slug}.vibedgames.com

Auth

Uses a polling flow: CLI generates a code, opens the browser, polls until the user confirms. Token stored at ~/.config/vg/auth.json.