rimitive-adapter

Adapter-based rendering unifies rendering logic across platform targets by implementing core tree operations like createNode, setAttribute, and appendChild. This decouples view module logic from platform-specific trees, allowing the same view code to render to DOM, Canvas, WebGL, or terminal without rewriting rendering logic.

To build a custom renderer for canvas and WebGL, implement the five core tree operations: createNode, setAttribute, appendChild, removeChild, and insertBefore. Pass your custom adapter to the view module factories to render view code directly to your target platform without altering view logic.

Adapter-based rendering supports server-side rendering and client-side hydration through optional lifecycle hooks like beforeCreate, onAttach, and beforeDestroy. Switchable adapters and parentContext support allow nested renderers to coexist, enabling seamless server-side rendering followed by client-side updates.

You can unit test custom renderers without platform deployment by using the built-in test adapter pattern. This testing adapter simulates tree operations and lifecycle hooks, allowing you to verify rendering logic and fine-grained reactivity in isolated unit tests without a DOM or canvas environment.

The limitation of a minimal core operation adapter is that it only provides createNode, setAttribute, appendChild, removeChild, and insertBefore. Complex platform-specific animations or advanced native mobile APIs require implementing optional lifecycle hooks manually, as the minimal core does not include them by default.