Browser‑Bridge lets you write server‑side Node functions that are automatically packaged and injected into the HTML sent to the client, eliminating separate build steps and allowing tight coupling of client and server code. It’s aimed at Node/Express developers who want to serve pages with only the JavaScript they actually need, using a simple API to define functions, singletons, and event handlers that appear as regular script on the browser.
Total donated
Undistributed
Share with your subscribers:
Recipients
How the donated funds are distributed
Support the dependencies of erikpukinskis/browser-bridge
Adds html here and there in different spots around DOM nodes
Send modules and their dependencies to the browser
build code that defines and calls functions in the browser
Wait for things to finish in other modules and other iframes
Generate unique ids for things and look them up on hashes
Talk to remote servers
Caches module singletons and orchestrates dependencies between them
Generate hashes from javascript objects in node and the browser.
Generate HTML for a web page
Do stuff in other peoples' browsers
Define tests with dependencies
JavaScript test spies, stubs and mocks.
Send stuff over HTTP
Support the repos that depend on this repository
Top contributors
erikpukinskis
469 contributions
Recent events
Kivach works on the Obyte network, and therefore you can track all donations.
No events yet