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

@v12-engine/create

v0.4.0

Published

A project to start a game from: npm create @v12-engine my-game

Readme

@v12-engine/create

Alpha. V12 is in active development: APIs, file formats and saves can change between releases. Pin an exact version for anything you ship. Docs: https://v12-docs.vercel.app

A project to start a game from, made with V12: its rules, its page, and the parts you choose.

npm create @v12-engine my-game

It asks where to make it, which starter, what the game is called, which parts it has, what server, and whether to make a git repository and install. --yes asks nothing; --help lists every flag.

| Starter | What it is | | ---------- | -------------------------------------------------------------------------------------------- | | empty | Hello world: a flat field and a scout to walk it. The default. | | melee | A whole RTS: two races and their heroes, bases and armies, against the computer. | | campaign | A campaign of three missions with a hero carried between them, drawn with the shared models. | | examples | What the engine can do, a small scene each, browsed from a list as three.js's examples are. |

npm create @v12-engine arena -- --yes --starter melee --server rooms --ratings

The parts: the map editor (--no-editor), a server of one game, of many games in rooms, or none (--server single|rooms|none), ratings (--ratings), a test of the rules (--no-tests), the shared art (--no-assets), a desktop app in an Electron shell (--desktop: npm run app opens it, npm run package makes the app to hand out), a git repository (--no-git), and installing at once (--install).

In code: createProject(folder, options) from @v12-engine/create.

The project it makes is yours: no attribution to this package is asked for in it. The package itself is MIT.

The whole guide is the docs' page Starting a project (docs/start/new-project.md in the repository).