Recently, Cesium for Unity introduced support for WebGL. However, as far as I can tell, the build docs have not yet been updated to include the WebGL-specific requirements.
There are two additional requirements that are currently not mentioned but are necessary for users to successfully package their projects for WebGL:
Ninja is required for WebGL Build support
Unity 6000.0.x or newer is required
Which stands in direct contrast to the recommendation of using Unity 2022.3 LTS.
The requirenment has been documented in a comment here:
I think it would be great to add mentions of this to the user docs. It took me some time to figure out why packaging for WebGL didn’t work.
Thanks for the detailed report — you’re absolutely right that this is confusing today.
For Web builds, Cesium for Unity currently requires Unity 6+ and web-specific setup, while developer-setup.md is still framed as general contributor setup and recommends Unity 2022.3 for that path.
You also correctly pointed out that the WebGL native build path uses CMake with -G Ninja in CompileCesiumForUnityNative.cs, so we should explicitly document Ninja/tooling expectations for web packaging workflows.
We’ll follow up on doc updates to separate base contributor requirements from Web-target requirements (Unity 6+, multithreading setting, hosting headers, and web packaging/tooling notes). Thanks again for raising this.