Peekazoo Flow Engine

This workspace package is the first flow-based engine milestone for the editor.

Public entrypoints:

• @peekazoo-gamemakers/game-engine

• @peekazoo-gamemakers/game-engine/runtime

• @peekazoo-gamemakers/game-engine/authoring

• @peekazoo-gamemakers/game-engine/validation

• @peekazoo-gamemakers/game-engine/types

• Generic template id: peekazoo-flow-v1

• Runtime package API: GameEngine.startPackage(zipBytes, mountEl, options?)

• Editor/runtime preview API: GameEngine.startFlow(config, mountEl, assetResolver?)

• Design canvas: 1920x1440, cover-cropped for wide landscape devices

• Spine runtime: @esotericsoftware/[email protected]

V1 supports config-only packages with manifest.json, game.json, and assets/. Tap and drag/drop are playable now; sequence, audio match, color/paint, trace, and puzzle are reserved for later component implementations.

Install

npm install @peekazoo-gamemakers/game-engine phaser

phaser stays a peer dependency for consuming applications.

Publish to npm

This repository is set up to publish the engine package from:

• packages/game-engine

The GitHub Actions workflow expects:

• the version in packages/game-engine/package.json to already be bumped
• an NPM_TOKEN secret configured in the repository (Settings → Secrets → Actions)

Recommended publish flow:

1. Update packages/game-engine/package.json version.
2. Commit the change.
3. Push the branch.
4. Create and push a tag like:

git tag engine-v0.0.3
git push origin engine-v0.0.3

That tag triggers the publish workflow and publishes the package to npm.