Production builds

How it works

The editor is a dev dependency, not a runtime. Nothing of it ships in a release build. The engine defines its build flags inline, so a branch behind a flag that is false drops out of the bundle.

A moku-game folder

A moku-game folder needs nothing here. The engine's release page names no agents. A debug build (moku-game build --debug) adds @moku-labs/editor/agent/page on purpose. The body of that page agent sits behind the inline guard __MOKU_GAME_DEV__ || __MOKU_GAME_AGENT__, so a release build, which defines both false, drops it.

A game with its own HTML page

Import the agent only behind the engine's dev flag, with a dynamic import. A production build defines __MOKU_GAME_DEV__ as false and drops it whole:

import { app } from "./game";

if (__MOKU_GAME_DEV__) {
  const { createApp, bridgePlugin, capturePlugin } = await import("@moku-labs/editor/agent");
  await createApp({ plugins: [bridgePlugin, capturePlugin], pluginConfigs: { registry: { game: app } } }).start();
}

What ends up in the bundle

Measured with Bun.build (browser, minified, the game itself external) in the editor's own test suite:

The editor's test bounds the dev agent at 124,000 B gzip. To stay under it, the phone only reads: the marks, the pass chains and the 2-minute history are built on the tools page.

Why a static import drops out too

The package is "sideEffects": false. The agent core, each agent plugin and each core config are created /* @__PURE__ */. So a static import used only inside if (__MOKU_GAME_DEV__) drops out too, and so does a type-only import of a plugin.

An agent export used outside that branch keeps what it references. A game entry that logs bridgePlugin.name outside the branch, with __MOKU_GAME_DEV__ false, still ships the agent without capture: 288,933 B minified, 119,887 B gzip.

Related

• On a phone: the debug build and its flags.
• Quick start: the dev entry of a game with its own page.