Player builds
How Loom bundles your UI into standalone player builds.
Player builds load the UI from:
Assets/StreamingAssets/Loom/Automatic build hook
Build your Unity player as usual. Loom adds these steps:
- Run
npm run buildin your UI directory. - Copy the output to
Assets/StreamingAssets/Loom/. - Include those files in the player.
If the UI build fails, Loom aborts the player build.
Requirements
The build machine needs:
- Node.js 22 or 24 LTS
- npm 10 or 11
- Installed UI dependencies (
node_modules) - A valid UI
package.jsonwith abuildscript
No Node.js in the shipped game
Node.js and Vite are development/build-time tools only. The shipped player loads
static HTML, CSS, JavaScript, fonts, and assets from StreamingAssets/Loom.
Verify the output
After a build, confirm that Assets/StreamingAssets/Loom/index.html exists and
that the folder contains your scripts, styles, fonts, and images. If the Editor works but the player
is blank, this folder is the first thing to check.
For automated builds, see CI/CD.