Skip to main content
The generated tableverse.config.ts already describes both packages:
Paths are relative to the config file. Keep package-lock.json beside tableverse.config.ts; Tableverse installs the complete npm workspace from this project root.

Upload your game

From the project root:
1

Check the project

2

Sign in

The CLI opens your browser to authenticate.
3

Upload

On the first upload, choose an existing game or create one. The CLI saves that choice in .tableverse/game.json.
4

Follow the build

The CLI prints a deployment dashboard URL and opens it when possible. Tableverse builds your engine and frontend from the uploaded workspace.
Check the game name and ID printed before every upload. A copied project may still contain a link to the original game.
Local .env files stay on your machine. Configure deployment secrets in Tableverse. For CI, set TABLEVERSE_GAME_ID to select the game without an interactive prompt.

Upload reference

Learn about project linking and upload behavior.