npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

window-pipe

v0.6.0

Published

Browser window to window two-way communication based on `window.postMessage()`.

Downloads

71

Readme

window-pipe

Browser window to window two-way communication based on window.postMessage().

Main features:

  • Seamless asychronus communication between pages in same or different domain.
  • Written in Typescript.
  • Below 10kB before gzipping.
  • Promise based connection establishing (handshake).
  • Timeout management on connection and request level.
  • Universal request command signature (method, parameters, timeout)
  • Request buffering until pipe connected.
  • Incomming requests listerner.
  • Promise based request sending with commands to "other side" recipient.
  • Posiblity to receive responses to send requests.

Getting started

To start communication between two browser windows you need reference to each window object. On each end of communication pipe page has to reference window-pipe lib, and have to establish a connection. Pages can be loaded from different origins (different domains).

Below example shows communication between "Parent" page that embeds iframe with "Child" window. Web module imports have been used. In node enviroment replace them with import WindowPipe from 'window-pipe'

Parent

import WindowPipe from 'https://cdn.jsdelivr.net/npm/window-pipe@latest'

// *** PIPE SETUP
// create window pipe instance
const pipe = new WindowPipe
// get reference to iframe containg child window
// iframe element with src attribute and id 'child' set to child window page has to be already present in DOM.
const childFrame = document.getElementById('child')

pipe.authKey = 'window-pipe-demo'

// pipe internal loger
// pipe.onLog = (l) => console.log(l)

// await for iframe loading
childFrame.addEventListener('load', () => {
  // set origin and window
  pipe.targetOrigin = childFrame.src
  pipe.targetWindow = childFrame.contentWindow

  // start connecting the pipe
  pipe.connect().then(() => console.log('CONNECTED!')) 
});

// subscribe to received event
pipe.onReceived = cmd => console.log(cmd)

// send pipe command named 'ping-from-parent' every 2,5 seconds
setInterval(() => {
  pipe.send({
    method: 'ping-from-parent',
    timeout: 0
  })    
}, 2500)

Child (frame)

import WindowPipe from 'https://cdn.jsdelivr.net/npm/window-pipe@latest'

// *** PIPE SETUP
// create window pipe instance
const pipe = new WindowPipe

// set origin and window
// origin have to have exact match with parent page url
pipe.targetOrigin = 'https://cdpn.io/xtech-dev/fullpage/Exeqjxm?nocache=true&view=' // change to url / host of the window that embeds child window.
// because child window is embed into iframe we will be communicating with parent window
pipe.targetWindow = window.parent

// set key that will identify created pipe (distinguish between other parties that will send messages to same window)
pipe.authKey = 'window-pipe-demo'

// pipe internal loger
// pipe.onLog = (l) => console.log(l)

// connect to the pipe
pipe.connect().then(() => {
  console.log('CONNECTED!')
})

// subscribe to received event
pipe.onReceived = cmd => console.log(cmd)

// send pipe command named 'ping-from-parent' every 3 seconds
setInterval(() => {
  pipe.send({
    method: 'ping-from-child',
    timeout: 0
  })    
}, 3000)

Live example

https://codepen.io/xtech-dev/full/Exeqjxm

Parent: https://codepen.io/xtech-dev/pen/Exeqjxm

Child: https://codepen.io/xtech-dev/full/Exeqjxm