// the find
creationix/topcube
Webkit Bindings for node
topcube wraps a WebKit/CEF window around a running HTTP server so Node.js apps can have a desktop GUI without leaving the web stack. It predates Electron by a couple of years and solved the same problem with a narrower scope: one window, HTTP only, child process. Abandoned in 2013.
The constraint of HTTP-only communication is actually a clean architectural choice — your app stays a normal web server and the GUI is just a browser pointed at localhost. The Windows path using CEF was ahead of its time. The API surface is tiny and honest about what it does and doesn't do.
Last commit is 2013 — WebKitGTK bindings against Node 0.x native addons will not build against anything made in the last decade. Mac support was never implemented, just left as a TODO. Electron, Tauri, and node-webkit (now NW.js) all superseded this and are actively maintained. The Windows binary is fetched from a dead URL via a Python script. There is no path to adoption here.