raven-component-authoring

To create a new UI component for WASM rendering, place the file under Sources/Raven/ and implement the appropriate rendering strategy using _render(with:) and toVNode to generate the required VNode/DOM output. Follow _CoordinatorRenderable patterns for state and event wiring.

DOM interop with JavaScriptKit works by using DOMBridge guidelines to safely bridge browser APIs while maintaining SwiftUI-like ergonomics. You wire events and handle state through the stable rendering pipeline, ensuring safe communication between the WASM environment and the browser DOM.

The best way to wire DOM events in a WASM UI component is by adhering to the _CoordinatorRenderable pattern and toVNode guidelines. This approach maintains state consistency and ensures events are properly routed through the VNode rendering pipeline to the browser.

Yes, you can create and apply SwiftUI-like modifiers for custom DOM rendering in Raven. The component authoring process supports building both composite views and primitive wrappers, allowing you to adjust DOM rendering and event wiring while preserving familiar ergonomics.

You need to use the _CoordinatorRenderable pattern when building new built-in Raven views or modifiers that require state management and event coordination. It provides a stable rendering pipeline that ensures proper VNode generation and DOM bridge interop.

A Raven UI component may not render correctly if it deviates from established rendering patterns, fails to properly implement toVNode, or ignores DOMBridge interop guidelines. Ensure your file structure under Sources/Raven is correct and that _render(with:) is properly configured.