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

wsockrelay

v0.1.1

Published

A HTTP/Websocket relay, capable of exposing your favorite game through that damn NAT wall.

Downloads

1

Readme

WSocketRelay

WSocketRelay is a Websocket-based UDP tunnel toolkit. It contains:

  • A server: the script you will run to host a relay server;
  • An exposer: use this to expose YOUR server (aka user server) to the aforementioned server;
  • A client: use this to connect to YOUR (or someone else's) user server through the relay server.

It is capable of relaying multiple user servers with only a single relay server.

How to Use?

This is usually needed when you want to use a secure Websocket tunnel to break through a firewall or NAT, or similar circumstances. Otherwise, why not just send your user server's IP to someone else?

  1. Host your user server.
  2. Either:
  • Host the relay server yourself (using ngrok to expose it, if necessary):
wsrserve <listen port>
  • Ask someone else to do it for you, while linking them to this page.
  1. Host your exposer, to relay your user server from and to the relay server:
wsrexpose <minimum local client port number (see below)> <relay server address> <your user server's listen port>
  1. The exposer will print out the Server ID to the console. Make sure to send that to whoever are your clients!

  2. Have your clients get WSocketRelay, so they can connect its WSocketRelay client to the user server through the new relay server:

wsrconnect <local listen port> <relay server address> <your Server ID>
  1. Have your clients point their client software to their own localhost, at the local listen port.

  2. ???

  3. Profit!

What is a "local client"?

UDP usually doesn't establish connections; it just throws packets around, with the UDP header, which, unimportant internal details aside, contains the source address and port.

Here, the exposer MUST make a different UDP socket, in a different port, for every client that connects to it, so that the server software can discern from each client, using only the port in the UDP packets' headers.

Attention

It was designed specifically for use with the first generation of the Unreal Engine (most specifically, the 1999 spawn of Unreal Tournament), though it doesn't work, due to a mysterious memory error in the game's side.