Hybrid Demos
Node Publisher to Browser Subscriber
Shows the same channel and payload contract working from a Node script into the browser.
Local workflowLocal setup requiredText Event
What this demo proves
A scriptable backend or utility runtime can publish the same canonical payloads that the browser demo receives without translation.
Platforms
Node.jsBrowser JavaScript
Payload types
StringJSON / object
Channel names
demo.text.basicCanonical text channel for browser-first and two-tab demos.
Example payload
{
"text": "hello world",
"label": "greeting"
}
Compatibility notes
Browser JavaScriptNative
Node.jsNative
PythonNative
p5.jsNative
ProcessingNative
ArduinoJSON wrapped
ESP32 / ESP8266JSON wrapped
Serial bridgeAdapter required
TouchDesignerNot yet supported
Run online
- Use the browser playground as the subscriber surface.
- Run the Node publisher locally against the same channel.
Run locally
- Run the Node publisher script with a valid API key.
- Subscribe from the browser playground on the same canonical channel.
Expected output
- The browser receives Node-published messages with the same payload shape defined by the shared scenario.
Troubleshooting
- If no events arrive, confirm both runtimes use the same channel and environment URLs.
Hybrid workflow
This page documents a local-to-browser bridge flow rather than a second hosted app. The browser subscriber lives in the instant demo, and the Node publisher lives in the repo script listed below.