Sync UI Dependencies / Loom Docs

Tools > Loom > Sync UI Dependencies updates your UI app’s @loomgui/bridge and @loomgui/vite-plugin versions to match the currently installed Unity package, and runs npm install.

When to run it

After upgrading the Unity package to a new version.
If the installed @loomgui/* versions do not match the Unity package.

There is no need to run it on every Editor start.

What it does

The menu installs the bundled @loomgui/bridge and @loomgui/vite-plugin tarballs into <ProjectRoot>/UI/.loom/, updates the matching entries in <ProjectRoot>/UI/package.json to point at those local files, and runs npm install.

Output streams to the Unity Console. When the install finishes, the Console reports [Loom] npm install completed.

After running

If the dev server is already running, it still serves the previous packages. Run Tools > Loom > Restart Dev Server to load the new versions. Otherwise, they load the next time you enter Play.

Recovery

If the menu errors out:

“Could not find the bundled UI dependencies” or “The bundled UI dependencies are missing”: the Unity package is missing its bundled tarballs. Reinstall the Unity package.
“No UI directory with a package.json was found”: use Setup UI Project; see Install and run Loom.
“…is managed by an npm workspace”: your UI app belongs to an npm workspace, so the menu leaves its dependencies alone. Update @loomgui/bridge and @loomgui/vite-plugin from the workspace root instead.
npm install exits non-zero: see the [Loom npm] lines in the Console. Common causes: Node missing from PATH (run node --version in a terminal to confirm), or a corrupt node_modules/ (delete it and re-run the menu).