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

quickpeer

v0.0.5

Published

A simple p2p peering library.

Downloads

6

Readme

quickpeer

Quickpeer is a simple peering library designed for easy plug & play p2p connectivity

Installation

npm install quickpeer

Usage

var peers = require('quickpeer');

// Events. Only 'message' is required.
// Each event can only have one handler, this is not a real EventEmitter

peers.on('message', (message, peer) => {
  // message comes in as a buffer
});

peers.on('peer', peer => {
  // Do something upon connection
  // 'peer' is just a regular Socket object
  peer.write('hello');
});

peers.on('error', (peer, error) => {
  // Handle errors
});

peers.on('close', (peer, errored) => {
  // Handle closed connections
})

var options = {
  seeds: ['seedurl.com'],
  port: 12345,
  // Optional:
  maxPeers: 8, // defaults to 8
  saveConfig: false, // true means quickpeer handles peer persistence. false means the dev handles it. defaults to false
  name: 'your-app-name' // only required if saveConfig is true
};

peers.start(options);

peers.broadcast('message');

// If you pass in a peer as a second argument to "broadcast" that peer will be excluded from the broadcast - useful for relaying messages.
peers.on('message', (message, peer) => {
  peers.broadcast('message', peer);
});

const activePeers = peers.getPeers();

peers.disconnect(() => {
  // done
}); // Close all peer connections

Limitations

In general, quickpeer is in alpha, and not battle-tested. It shouldn't be relied on for anything critical.

  • Quickpeer currently assumes all peers are communicating on the same port.
  • Due to the way peering works, messages that begin with the word 'peer' will not be passed to the message handler. A future version will provide a workaround.
  • If a peer sends a flood of messages, they may all arrive at once. It's your responsibility to implement message parsing/delimiters.
  • Quickpeer doesn't try to form a reasonable network topology, it just peers willy nilly.

License

MIT