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

p2p-node

v0.1.1

Published

Create a peer-to-peer relationship

Downloads

25

Readme

P2P Node

Low-level library to handle peer-to-peer traffic on Cryptcurrency networks. A raw socket object in Node emits data events whenever the stream is updated. This library sits on top of a raw socket connection, and instead of emitting data events every time the stream updates, it waits and emits message events whenever a complete message has arrived.

It uses the Bitcoin protocol structure to parse incoming messages; any stream that's encoded as follows can be parsed:

  • 4 bytes: Uint32: Magic Bytes: Flag the beginning of a message
  • 12 bytes: Char: ASCII string identifying the message type, null-padded to 12 characters long
  • 4 bytes: Uint32: Payload length
  • 4 bytes: Uint32: Checksum: First four bytes of sha256(sha256(payload))
  • variable bytes: Payload data

The default Magic Bytes and default Port to connect to are set to the Bitcoin protocol.

Usage

var Peer = require('Peer').Peer;

var p = new Peer('remote.node.com');
p.on('connect', function(d) {
  console.log("I'm connected!");
});
p.on('message', function(d) {
  console.log("I got message "+d.command);
});

Peer is an EventEmitter with the following events:

Events

connect

When the socket connects

Data object passed to listeners:

{
  peer: Peer
}

error

If the socket errors out

Data object passed to listeners:

{
  peer: Peer,
  error: Error object from Socket
}

end

When the socket disconnects

Data object passed to listeners:

{
  peer: Peer
}

message

When a complete message has arrived

Data object passed to listeners:

{
  peer: Peer,
  command: String,
  data: Raw payload as binary data
}

commandMessage

An alternate version of the peerMessage event; in these events, the command of the message is used as the event name (i.e. command 'foo' would cause a fooMessage event).

{
	peer: Peer,
	data: Raw payload as binary data
}