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

@slashd/wire

v0.0.4

Published

Cross communication channel

Downloads

7

Readme

Wire

Wire is a tiny library that allows to instances of a component to communicate to each others by using a little event broadcaster.

The main purpose is to add syncing capability to specific instances, with the possibility to include/exclude some of them in the overall sync flow.

Each instance can be configured in order to orchestrate how the signals flow from one to the others.

By default every instance sends messages to others that subscribe to the same event type.

The following properties can be used, alongside the default values:

  • wireSenderEnabled: true enable/disable the ability of a specific component to send events
  • wireSenderName: '' specify a sender name that is useful with wireReceiverAllowed
  • wireReceiverAllowed: [] specify sender names to receive events only from them
  • wireReceiverEnabled: true enable/disable the ability of a specific component to receive events

https://user-images.githubusercontent.com/870788/217051507-ebb8dd5c-8dc2-467c-8d6e-7ed2b7347787.mp4

This is another example:

https://user-images.githubusercontent.com/870788/218159272-3c773ab2-c262-4b5b-9752-2d24451695ea.mp4

Installation

With your favorite package manager:

npm install @slashd/wire

Then, use it in the browser:

<script src="node_modules/@slashd/wire/dist/slashd-wire.min.js"></script>

or with ES6 in a module or within a bundler:

import SlashdWire from '@slashd/wire'

API

To implement such syncing capability, your component needs to implement some methods of the library, that are:

  • SlashdWire.add to add a the instance into the broadcaster
  • SlashdWire.send to send a specific event with payload in broadcast
  • SlashdWire.on to subscribe a specific event in order to receive a payload

Events can be anything, such as update, whatever, etc, your call.

The only requirement is an UID per each component

Additional methods are:

  • SlashdWire.remove to remove an instance from the broadcaster
  • SlashdWire.off to unsubscribe from an event

Here a minimal component that implements the required methods:

import SlashdWire from '@slashd/wire'

const Comp = () => {
  
  // minimal config
  const config = {
    wireSenderEnabled:true,
    wireSenderName:'',
    wireReceiverAllowed: [],
    wireReceiverEnabled:true,
    uid: Math.random()
  }
  
  // add it to the broadcaster
  SlashdWire.add(config)
  
  // send the 'update' event to other instances
  SlashdWire.send('update', {uid: config.uid, data})
  
  // receive the 'update' event from other instances
  SlashdWire.on('update', config.uid, payload => {
    // do something with the payload
  })
}


// make instances of the component
new Comp()
new Comp()
new Comp()

The library is responsible to handle the messages between instances only. What should happen on each event received it's up to you.

Use Broadcast Channel

When you add a client, you can pass an optional parameter broadcast with a string value which is the BroadcastChannel name to allow cross communication between same-origin iframes.

Contribute

Install dependencies:

npm i

Start the watcher

npm start