build(react): output bundle to its own dist/ instead of SignallingWebServer/www/

[mcottontensor]

Summary

Both reference frontend implementations were writing to SignallingWebServer/www/ with clean: true. npm run build --ws walks workspaces in declared order, so:

1. Frontend/implementations/typescript builds → writes player.html, player.js, all UI assets to www/.
2. Frontend/implementations/react builds → clean: true wipes everything the TS impl just wrote, then writes only index.html / index.js.

After that, start.sh's setup_frontend() checks if [ ! -d www ] (SignallingWebServer/platform_scripts/bash/common.sh:229), sees www/ exists, and skips its own rebuild. Wilbur ends up serving the React impl's minimal page — auto-connect, no overlay, white background — instead of the expected TS reference frontend with its Click to start overlay and settings UI.

The fix points the React webpack output at a local dist/ directory. The two implementations no longer collide. WEBPACK_OUTPUT_PATH is honoured for symmetry with the TS impl, and the readme picks up a short note showing how to have Wilbur serve the React bundle via --http_root.

Repro before / verification after:

$ rm -rf SignallingWebServer/www \
         Frontend/implementations/react/dist \
         Frontend/implementations/typescript/dist
$ npm run build
$ ls SignallingWebServer/www/
# before: index.html  index.js  (React impl, TS impl gone)
# after:  player.html  player.js  showcase.html  stresstest.html  uiless.html ...
$ ls Frontend/implementations/react/dist/
# after:  index.html  index.js

Test plan

• rm -rf then npm run build at root — www/ ends up with TS impl, React lands in its own dist/
• Lint clean (npm run lint --workspace Frontend/implementations/react)
• Manual: start.sh after a root build serves the proper UI
• Manual: start.sh --http_root=$(pwd)/Frontend/implementations/react/dist serves the React impl

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3b1234c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mcottontensor]

💚 All backports created successfully

Status	Branch	Result
✅	UE5.5
✅	UE5.6
✅	UE5.7

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details