Displaying 1 to 20 from 27 results

postmate - 📭 A powerful, simple, promise-based postMessage library.

  •    Javascript

A powerful, simple, promise-based postMessage iFrame communication library. Postmate is a promise-based API built on postMessage. It allows a parent page to speak with a child iFrame across origins with minimal effort.

player.js - Interact with and control an embedded Vimeo Player.

  •    Javascript

The Vimeo Player API allows you to interact with and control an embedded Vimeo Player. Already have a player on the page? Pass the element to the Vimeo.Player constructor and you’re ready to go.


  •    Javascript

A library for passing data structures between sandboxed environments in the browser via postMessage.

hello-frame-rpc - client/server-style RPC for iframe postMessage communication

  •    Javascript

This package provides some setup on top of frame-rpc to configure the postMessage origins and window.parent traversal with a hello message before dropping down into the primary RPC mechanism.Now visit http://localhost:9001 in a browser. You will see a greeting, "hello from the server!!!" rendered to the page and a message in the console: n=555.

page-bus - share an event emitter among pages and frames on the same domain

  •    Javascript

This module works offline and does not rely on any network IO.Behind the scenes, the localStorage API and the window 'storage' event is used to synchronize cross-page events.

penpal - A promise-based library for communicating with iframes via postMessage.

  •    Javascript

Penpal is a promise-based library for securely communicating with iframes via postMessage. The parent window can call methods exposed by iframes, pass arguments, and receive a return value. Similarly, iframes can call methods exposed by the parent window, pass arguments, and receive a return value. Easy peasy. The total size of the library is approximately 5 KB minified and 2 KB gzipped. It has no dependencies.

endpoint.js - Web application discovery, execution and streaming library

  •    Javascript

Endpoint.js enables modules within a web application to discover and use each other, whether that be on the same web page, other browser windows and tabs, iframes, servers, web workers and processes in a reactive way by providing discovery, execution and streaming interfaces. Take a look at our Basic Usage, Configuration Guide, API at a Glance, Advanced Usage, Security Guide, read the suggested integration document, or check out the Architecture Diagram.

cross-domain-events - Event-like api for postMessage to send objects between cross-domain frames

  •    Javascript

An event-like interface to postMessage for cross domain communication. postMessage was implemented in Internet Explorer 8, but only supports sending text strings. Modern browsers can send objects, but if you want to listen for different kind of objects you have to implement your own delegation.

promise-window - Lightweight wrapper around window.open() that adds Promise and postMessage support

  •    Javascript

Grab a copy of promise-window (development version). Instantiating the PromiseWindow prototype gives you more control. The following example shows how to close the window after 30 seconds.

self-addressed - Transform postMessage calls to return a promise

  •    Javascript

Available on NPM and bower under name self-addressed. Provides single function stamp(mailman, address, data), that returns a Promise.


  •    Javascript

crossdomain-xhr, is a client-side javascript library with no external dependencies. This library solves the problem of cross-domain HttpRequest by utilizing the standard XMLHttpRequest. Based on the system setup, this library can leverage either CORS or IFrame PostMessage. For IE 8 & 9 support, it is recommended to use IFrame PostMessage. The following example uses "CORS" with polyfill "PostMessage".

postmessage-client-server - A simple promise-based client and server to communicate between pages and iframes with postmessage

  •    Javascript

A simple promise-based client and server to communicate between pages and iframes with postmessage. All data passed will be serialized with JSON.

tabtalk - Secure, encrypted cross-tab communication in the browser

  •    Javascript

Messages are sent by postMessage, allowing for cross-origin usage (with the use of custom config properties), and the data in the message is encrypted with krip under the hood. Creates a new TabTalk instance where the window it is executed in (itself) is the tab. The instance returned allows you to open children, and will automatically glean its parent if it was opened from another TabTalk instance.

window-post-message-proxy - A generic messaging component for orchestrating promise based messages to/from a hosting application and an iframed component over the window

  •    TypeScript

A library used in place of the native window.postMessage which when used on both the sending and receiving windows allow for a nicer asynchronous promise messaging between the windows. When sending messages using the proxy, it will apply a unique id to the message, create a deferred object referenced by the id, and pass the message on to the target window. The target window will also have an instance of the windowPostMessage proxy setup which will send back messages and preserve the unique id. Then the original sending instance receives the response message with id, it will look to see if there is matching id in cache and if so resolve the deferred object with the response.

ipfs-postmsg-proxy - :performing_arts: Proxy to an IPFS over window.postMessage

  •    Javascript

The proxy uses postmsg-rpc under the hood to create an object which looks like an IPFS instance on the web page. This is just an object with "stubs" (functions) that use window.postMessage to communicate with a real IPFS node running in the browser extension. postmsg-rpc allows us to create these stubs and expose methods on the IPFS node without having to deal with the complexities of window.postMessage. We're using interface-ipfs-core to test our call stubs which are hooked up to a js-ipfs/js-ipfs-api on the other end. If the tests pass we know that the proxy is doing a good job of passing messages over the boundary.

We have large collection of open source products. Follow the tags from Tag Cloud >>

Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.