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

@source-health/js-bridge

v1.0.0-alpha.0

Published

Zero-dependency typescript library for cross-frame communication

Downloads

17

Readme

JS Bridge

This is a low-level library that facilitaties communication between web workers orwindows using a simple Promise-based API

Feaures

  • 🔁 Parent and child can both expose methods and/or events.
  • 🔎 Optional strong typing of method names, arguments, return values, and more.
  • 🔗 Support multiple concurrent connectionz.
  • 🌱 Zero dependencies - about 8KB before gzip.
  • 👐 Open source (MIT)

Usage

The first step of using the Bridge is to declare a channel that identifies the two parties. This library currently supports WindowChannel, which enables communication between two Windows.

Then, you can initialize the host:

import { Bridge, WindowChannel } from '@source-health/js-bridge'

const channel = new WindowChannel({
  localWindow: window,
  remoteWindow: frame.contentWindow,
  expectedOrigin: 'https://my.origin',
})

const host = Bridge.host(channel)

host.connect().then(() => {
  console.log('connected')
})

And initialize the guest:

import { Bridge, WindowChannel } from '@source-health/js-bridge'

const channel = new WindowChannel({
  localWindow: window,
  remoteWindow: window.parent,
  expectedOrigin: '*',
})

const guest = Bridge.guest(channel)

host.connect().then(() => {
  console.log('connected')
})

Once both are intialized, you can start communicating!

Events

Events are fire-and-forget notifications that can be broadcast from one side of the bridge, and observed from the other.

On the host:

bridge.on('someEvent', (data) => console.log(Data))

On the guest:

bridge.broadcast('someEvent', { key: 'value' })

Note that events can be broadcast from either side. Guests can receive events from the host, and host can receive events from the guest. There is no notification of an event being received. The protocol only emits the event.

Methods

Methods are bidirectional request/response call pairs. Calling methods can accept arguments and return values. All calls are asynchronous at the protocol layer.

On the host:

const bridge = Bridge.host(channel, {
  methods: {
    token: () => 'VerySecureValue'
  }
})

On the guest:

const guest = Bridge.guest(channel)
const token = await guest.call('token')

// VerySecureValue

Methods have a default timeout of 5s (5000ms), which can be configured when instantiating the Bridge.