@twinlight/three

three.js integration helpers for TwinLight. TwinLight is a remote native renderer, not a WebGL implementation, so this package mirrors three.js scene state into TwinLight while local three.js remains useful for controls, overlays, gizmos, and migration adapters.

60-second scene bridge

import { SceneBridge } from "@twinlight/three";

const bridge = new SceneBridge((message) => {
  client.send(message);
});

bridge
  .bindScene(scene, { camera, controls })
  .start();

Limited renderer-like adapter

import { TwinLightRenderer } from "@twinlight/three";

const renderer = new TwinLightRenderer({ client });
renderer.setSize(1280, 720);
renderer.render(scene, camera);

TwinLightRenderer.render(scene, camera) mirrors scene and camera state. Final pixels arrive asynchronously from the native renderer through the selected TwinLight viewport transport.

Professional integration notes

• SceneBridge is the public facade name for the existing diff engine.
• Viewport composes the remote surface with a local transparent three.js overlay.
• Pure mappers such as cameraMessage, transformMessage, and materialMessage remain stable named exports for tests and custom integrations.

Not supported

• TwinLightRenderer is not a THREE.WebGLRenderer subclass.
• No WebGL render targets, shader compilation, postprocessing composer parity, or immediate readback.
• No automatic translation of arbitrary ShaderMaterial code.