Local sessions - tableverse-kit

Create your client with the function you use throughout your frontend:

import { createTableverseClient } from "@tableverse-kit/client";
import type { executor } from "token-race-engine";

type Game = typeof executor;

const client = createTableverseClient<Game>({
  viewer: "p1",
});

Start the local server, frontend, and developer shell from the project root:

npm run dev

Options

Option	Default	Purpose
`serverUrl`	`"http://127.0.0.1:5100"`	URL printed by `tvk dev`.
`viewer`	`"p1"`	Player ID used for local views and commands.

The developer shell owns the match. Its setup form takes the number of seats, the RNG seed, and your game’s setup input, and starting the match initializes the in-memory session. The shell then frames your page and passes the seat to it, so both options above apply when you open your frontend’s own dev server URL directly. Use the shell’s control strip to switch seats, Reset for a fresh match with the same parameters, and Exit game to return to the setup form.

Wait for the connection

try {
  await client.ready();
  render(client.getView());
} catch (error) {
  renderConnectionError(error);
}

Calls to execute, discover, or getAvailableCommands reject with a TransportError if the client is not ready.

Use a different port

Start the server with --port and pass the same base URL to the client:

npx tvk dev --port 5200

const client = createTableverseClient<Game>({
  serverUrl: "http://127.0.0.1:5200",
});

Tableverse supplies the session URL, player identity, roster, seed, and setup input for published games. These options configure your local session.

Render state changes

Subscribe and update your interface.

​Options

​Wait for the connection

​Use a different port

Render state changes

Options

Wait for the connection

Use a different port