I'm testing my 3D application using this library. It works perfectly on http://localhost:4200. However, after building the application and deploying it to our on-premises environment, the 3D scene fails to render.

I also tested the application in the development environment by accessing it via http://:4200 from another machine. The issue persists—the application loads, but the 3D scene is not rendered correctly.

Here is AI finding about the bug:

crypto.randomUUID() is a secure-context-only API — breaking Three.js rendering over LAN HTTP

In libs/core/src/lib/instance.ts:129:

instance.ngt_id = crypto.randomUUID();

Browsers only expose crypto.randomUUID on secure contexts (https:// or localhost). On any plain http:// origin — including LAN IPs like 192.168.1.x — the function is undefined, causing a silent TypeError inside the effect created within afterNextRender. Because the crash is swallowed by angular-three's zone-external rendering loop, no console error appears and the 3D scene simply never initializes.

crypto.getRandomValues() is available in non-secure contexts and can generate a compliant UUID v4.