A monorepo of original browser games, built with TypeScript + Vite and deployed together to a single GitHub Pages site. The repo uses npm workspaces: one root npm install, one root lockfile, and shared hoisted dependencies across every game.

Not affiliated with any game studio. All names, characters, abilities, items, and lore in these projects are original works inspired only by generic genre archetypes.

Each game lives in its own workspace under packages/, described by a game.json next to its package.json. That file is the single source of truth: the table below, the landing page, and the deploy workflow are all generated from it.

Every game ships with its own README.md, tests, and (where applicable) asset generators under tools/. Some games add libraries of their own on top of the shared Vite + TypeScript + Phaser 3 base - the Stack column above lists what each one actually uses.

The original single-game Arena Champions README now lives at packages/champs/README.md.

open-games/
├── package.json              # root: npm workspaces + fan-out scripts
├── package-lock.json         # single lockfile for all workspaces
├── LICENSE                   # single Apache-2.0 license for the whole repo
├── CONTRIBUTING.md           # repo-wide rules + new-game checklist
├── .gitignore                # consolidated ignore rules
├── scripts/
│   ├── lib/games.mjs         # loads + validates every packages/*/game.json
│   ├── gen-readme.mjs        # regenerates the tables in this README
│   └── new-game.mjs          # scaffolds packages/<slug> from the template
├── site/
│   ├── index.template.html   # landing-page markup (no game data in it)
│   └── build.mjs             # renders the landing page from every game.json
├── packages/
│   ├── _template/            # starter for a new game; not a workspace
│   └── <slug>/               # one workspace per game, each with a game.json
└── .github/workflows/deploy.yml   # builds every workspace + landing page, deploys to Pages

Nothing outside packages/<slug>/ names an individual game or counts how many there are.

Requires Node 22 and npm 11.

Install everything with a single root install - npm workspaces hoist and share dependencies across all games, and produce one root package-lock.json:

npm install            # from the repo root; installs all workspaces

Do not run npm install inside individual packages - the workspaces setup handles them.

Use npm's -w (workspace) flag to target a single package, where <slug> is any directory under packages/:

npm run dev -w packages/<slug>        # start the Vite dev server for one game
npm run build -w packages/<slug>      # type-check + production build for one game
npm run test -w packages/<slug>       # run one game's unit tests
npm run typecheck -w packages/<slug>  # type-check only, no emit

Each game builds with Vite and emits to packages/<slug>/dist.

The root package.json fans out across all workspaces via --workspaces --if-present:

npm run build        # build every game, then generate the landing page
npm run build:games  # build every game only
npm run build:site   # generate the landing page into _site/ only
npm run test         # run every game's tests
npm run typecheck    # type-check every game
npm run docs:readme  # regenerate the tables in this README from game.json
npm run docs:check   # verify those tables are up to date (no writes)
npm run new-game     # scaffold a new game; see below
npm run thumbs       # re-capture the landing-page thumbnails (maintainer tool)

Four steps, none of which touch a shared file:

1. Scaffold it. npm run new-game -- --slug foo --title "Foo Quest" copies packages/_template to packages/foo and substitutes the placeholders.
2. Describe it. Fill in packages/foo/game.json (genre, summaries, stack) and set status to playable when it is ready to list.
3. Wire the install. Run npm install from the root so the new workspace is linked.
4. Verify. npm run typecheck && npm run test && npm run build, then npm run docs:readme to refresh the tables above. Run npm run thumbs once the game renders, so the landing page shows a real screenshot instead of a placeholder tile.

The landing page, the tables in this README, and .github/workflows/deploy.yml all pick the game up on their own. See CONTRIBUTING.md for the full checklist and the original-naming rules.

Every game deploys to a single GitHub Pages site at:

https://savagemanage.github.io/open-games/

The Pages workflow at .github/workflows/deploy.yml builds every workspace, collects each packages/<slug>/dist into a <slug>/ subpath by globbing (no game is named in the workflow), generates the root landing page, and publishes them together. Each subpath matches the base configured in that game's vite.config.ts (production base /open-games/<slug>/, dev base /):

Enable Pages once under Settings → Pages → Build and deployment → Source: GitHub Actions.

See CONTRIBUTING.md for repo-wide rules: the new-game checklist, the checks a change has to pass, and the original-naming policy. Individual games may add their own guide on top - for example packages/wirework/CONTRIBUTING.md.

This project is licensed under the Apache License 2.0. A single LICENSE file at the repo root applies to every workspace; each package's package.json also declares "license": "Apache-2.0".

© 2026 Janghoon Lee