Build and release a game

npm run build turns a game into a static folder, dist/, that any web host can serve: the game, its assets, its service worker and its licences. A release build adds the gates a game must pass before people play it: provenance locked, budgets, translations, voices, playtests and the exhaustive proof. This page says what each command checks, in which folder it runs, and what to look at before you send the link.

What you get

A dist/ folder, checked file by file, ready to upload: an installable web app (PWA) that plays offline after the first visit, whose every file is accounted for with its licence under dist/licenses/.

Context and versions

The same game builds in two places, with different commands:

The page applies from 4.2.5, when the command became quest-n-click (before, web-scumm). The created project and its build and release commands exist since 3.9.0; npm start is a Node launcher since 4.1.8.

Prerequisites

• Node 22.12 or later, the project installed (npm install in a created project, npm ci in the engine repository). See Requirements.
• Python 3 with the packages of requirements.txt (Pillow first): npm run assets turns art/ and audio/ into public/assets, and a created project's build runs it every time. In a created project the file is node_modules/quest-n-click/requirements.txt.
• ffmpeg when the game has sounds, music or video to encode, and for a release when the game declares music in stems (validate --release measures them with ffprobe).
• A game that passes its checks: Checking your game. Building runs them again and stops on the first that fails.

Where to run the commands

• "In the created project": the folder quest-n-click create made, the one with game/ and package.json.
• "In the engine repository": the clone of wanoo/quest-n-click. The game built is the one GAME names, else the one npm run game selected, else package.json → config.game, else demo.

Steps

1. Prepare the assets when images or sounds changed.

   # in the engine repository (public/assets is committed there: commit what this writes)
   npm run assets

   copy

   In a created project, public/assets is not committed (its .gitignore lists it) and npm run build runs assets itself.

2. Build.

   # in the created project
   npm run build

   copy

   It runs, and stops at the first failure: assets; verify (validate, solve, translations status, lint, playtests); the Vite build into dist/; then the check that every file of dist/ is accounted for.

   # in the engine repository
   npm run build

   copy

   It runs check (types, the Node tests) then build:game: verify:game (validate, solve, solve by chapter, variants, translations status, lint, playtests), the Vite build, verify:dist, check:spoilers and audit:assets.

3. Run the release gates before a public release.

   # in the created project
   npm run release                 # or: npm run release -- --commercial

   copy

   release runs assets, verify and the build, then: validate --release (the provenance lock, placeholders, ids), weight --release (what a phone downloads, against the game's assetBudgets), i18n status, voices check --release, playtests --strict, solve --prove (every reachable state), solve-reality, and with --commercial validate --commercial --errors (no exception, no placeholder, no non-commercial licence); last, the check of dist/.

   # in the engine repository
   npm run verify:release          # or: npm run verify:commercial
   npm run prove:game

   copy

   The template's art is a placeholder: a release refuses it until each file is replaced, reviewed and locked (npx quest-n-click provenance --lock in a created project, npm run provenance -- --lock in the engine repository). See Asset provenance.

4. Seal the ending, only for a game with a sealed ending, in the engine repository: seal the real outcome, build, commit, then deploy. The whole procedure is in The sealed ending.

   # in the engine repository, with games/<id>/private/ending.config.ts filled in
   npm run seal -- --outcome=<key>
   npm run build

   copy

5. Upload dist/ to a static host (next section), then play the live version.

   # in the engine repository: plays the deployed game to its ending, in a phone-sized browser
   node scripts/e2e.mjs https://<your-site>/

   copy

   scripts/e2e.mjs is in the engine repository only; in a created project, play the live site by hand to the end.

What the build ships

npm run build type-checks (in the engine repository), tests, bundles and audits the output. The result is a PWA:

• the service worker caches the app shell (code, styles, the page, fonts used by the page, the icons) at install;
• images and sounds are cached on first use, and the engine warms in the background the current room, the rooms one exit away and their audio;
• by default (GameDef.offline: 'full') it then fetches the rest of the game during idle time, so the whole game plays offline after the first visit; with offline: 'nearby', rooms never visited nor warmed may still need the network. Rooms are never all downloaded up front before the game starts: that keeps the first visit light.

The pause menu tells the player whether the whole game is cached. The details are in Sub-path, cache and service worker.

Every build ends by removing from dist/assets the files that are not this game's and writing dist/licenses/: the engine's LICENSE, LICENSE-ASSETS, CREDITS.md from the game's provenance, THIRD_PARTY_NOTICES.txt and assets-manifest.json (each file's path, author, source, licence, SHA-256 and status). The check that follows refuses any other file in dist/, and a locked file or a notice that is missing.

Deploying

dist/ is static: any static host serves it.

• GitHub Pages: a workflow builds with BASE_PATH=/<repo>/ and deploys dist/. For a created project, which has no workflow, copy the one in Publish on GitHub Pages.
• Clever Cloud: a Node application that builds on deploy and serves dist/; see The static game on Clever Cloud.
• Netlify, Cloudflare Pages, nginx, a bucket…: Other static hosts.

Under a sub-path (https://<user>.github.io/<repo>/), build with BASE_PATH=/<repo>/; at the root of a domain, no BASE_PATH. Every path (scripts, styles, manifest, icons, service worker, the sealed ending's file) follows it:

# in the created project or the engine repository: the same build as Pages, locally
BASE_PATH=/my-repo/ npm run build

What goes wrong under a sub-path, with the cache or with a half-uploaded site: Sub-path, cache and service worker, incomplete deploys, going back.

In the engine repository, games/<id>/private/ (photos, raw sheets, the sealed ending's configuration) is never sent: .gitignore excludes it, and nothing in it is copied into dist/. A created project's .gitignore lists only node_modules, dist, .cache and public/assets: keep private files outside game/, or add them to it.

Expected result, and how to check it

• The command ends without error and dist/ holds index.html, sw.js, manifest.webmanifest, assets/, icons/, fonts/ and licenses/.
• npm run preview serves it on http://127.0.0.1:4173/: play it there before uploading.
• After the upload, play the live site to the end on a real phone, in landscape; open the pause menu and wait for "complete" on its "Offline" row before you test offline.
• The last checks before you share the link (a real phone, someone else playing without help, the sealed ending) are in Checking your game.

Common errors

Files or data changed

• dist/: emptied and rewritten by each build (not committed).
• public/assets/ and .cache/refs.json: written by assets (committed in the engine repository, not in a created project).
• games/<id>/data/ (engine repository): the sealed ending's file, written by seal.
• Nothing in node_modules/quest-n-click: the engine is read, never written.

Recovery or going back

A build changes nothing you cannot rebuild: delete dist/ and run it again. To put an earlier version back online, deploy the build of an earlier commit; what players' caches and saves do then is in Going back.

References

• cli/quest-n-click.mjs: what build and release run in a created project.
• package.json: build, build:game, verify:release, verify:commercial, prove:game, start in the engine repository; scripts/start.mjs.
• tools/dist.ts: what dist/ may hold; tools/validate.ts: the release and commercial gates.
• vite.config.ts: the build and the service worker.
• npm scripts, The package.