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

gotti-channels

v0.2.61

Published

Isolated channel communication for gotti.js

Downloads

20

Readme

Just like how I redid my messenger project, I wanted to refactor the old centurm-channels project to promote custom protocols, now all messaging functions take arrays as parameters and will send them over the network flatly. It appends its own protocols at the end of your array which works very efficiently and allows you to design your own protocols starting from index 0.

The back channel now fires off an onClientMessage as well as an onMessage for messages that were sent without the client flag.

They will look like

    client = new Client('test_client');

    // link to channel first
    await client.linkChannel('test_channel');

    // then set it as processor (not async any channel can start processing any client data, it's really just a ping to let the back channel know)
    client.setProcessorChannel('test_channel');

    // now you can send messages
    client.sendLocal(['protocol', 'data', 'moreData', 'moreMoreData']);


    // over on the back channel you receive them like -
    onClientMessage((clientUid, message) => {
        console.log(clientUid) // 'test_client'
        console.log(message[0]) // 'protocol'
        console.log(message[1]) // 'data'
        console.log(message[2]) // 'moreData'
        console.log(message[3]) // 'moreMoreData'
        console.log(message[4]) // 'test_client'
    });

the string at index 4 was appended by the front channel when sending the message across. This is so the back channel knows to run the onClientMessage and you can hook into it and run logic on the client with whatever protocols you define.