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

reliable-udp

v0.2.0

Published

Reliable communication over a udp socket.

Downloads

12

Readme

DEPRECATED

This library is deprecated in favor of node-udp-messaging which has defined more managable goals.

Current state of this library does not allow stable transfers of big ammounts of data.

node-reliable-udp Build Status Package Version License Dependencies codecov

A reliable communication protocol over UDP with holepunching for Node.js.


Goal

Implementing NAT holepunching with TCP is very tricky and does not work on every configuration. This project aims to deliver a tool to establish a reliable communication stream (TCP-like) over UDP for use in P2P systems. Communication stability has the priority over speed in this project.

Installation

Node >=8.9.0 is required.

npm install --save reliable-udp

To perform tests use:

cd node_modules/reliable-udp
npm t

Usage

Beware this project is still in development. There may be serious bugs or performance issues over time.

(async () => {
    // Create a reliable UDP socket
    const ReliableUDPSocket = require('reliable-udp');
    const server = new ReliableUDPSocket({ port: 12345 });
    await server.bind();

    // Connect to another peer
    const peer = await server.connect('127.0.0.1', 12345);

    // Send some raw data as a stream
    const data = Buffer.from("SomeGenericDataHere");
    peer.sendBuffer(data);

    // Receive raw data as a stream
    peer.on('data', (data) => {
        console.log(`Received: ${data}`);
    });

    // Execute holepunching (get an address and port that another peer over the internet can use to reach this peer)
    const hole = await server.discoverSelf();

    // Close a particular session
    peer.close();

    // Close all current sessions and unbind
    server.close();
})();

Contributing

The source is documented with JSDoc. To generate the documentation use:

npm run docs

Extra debugging information is printed using the debug module:

DEBUG=reliable-udp:* npm t

The documentation will be put in the new docs directory.

To introduce an improvement please fork this project, commit changes in a new branch to your fork and add a pull request on this repository pointing at your fork. Please follow these style recommendations when working on the code:

  • Use tabs (yup).
  • Use async/await and/or Promise where possible.
  • Features must be properly tested.
  • New methods must be properly documented with jscode style comments.