Prepare an H5 build

Plain HTML + JavaScript

Place the entry HTML, scripts, styles, and assets in the output folder. A self-contained game can be a single index.html.

dist/
├── index.html
├── main.js
├── style.css
└── assets/

No npm install or compilation is needed. Check relative asset references, start an HTTP preview, verify the core gameplay, then follow Publish and update. Star Sprint’s plain version lives in plain/dist; upload that version with --dir ./plain/dist.

Vite or Webpack

From the folder containing package.json, follow the project’s README and scripts. The supplied Vite examples use the following commands. Stop the development server before building and previewing.

npm ci
npm run dev
npm run build
npm run preview

Use a relative Vite base, or your Webpack project’s relative publicPath:

import { defineConfig } from 'vite';
export default defineConfig({ base: './' });

The two supplied Vite projects require Node.js 20.19+ or 22.12+; the recorded run used 25.7.0. Other projects have their own requirements and script names. dev is for development, build produces the output, and preview serves it. Confirm dist/index.html and every asset exist and work.

React/Vue are UI frameworks; Vite/Webpack are build tools. All are optional for a plain HTML/JS game. Continue with the Star Sprint example or the common publishing flow.

Source: Combos developer integration guide , checked on 2026-10-08 with CLI v1.14.2. Example results refer to the original recorded runs.