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

wsproxy

v1.2.32

Published

This is a websocket to tcp proxy, written in node.js. It is dynamic and will proxy to various tcp servers.

Downloads

97

Readme

wsProxy

Build Status

This is a websocket to tcp proxy, written in node.js. It is dynamic and will proxy to various tcp servers.

Installation

npm install wsproxy -g

Usage

wsproxy [-p PORT] [-t THREADS (# of threads to spawn)] [-s ENABLE_SSL] [-k KEY_FILE] [-c CERT_FILE]
  • -p Port to bind wsProxy to
    • If no port is specified it will default to process.env.PORT or port 5999.
  • -a List of allowed servers to proxy to
    • By default wsProxy will proxy to any ip:port, this is a major risk, since malicous users may use your wsProxy server for illegal activity, or any other use other then connecting to your athena server.
    • The list of IP:PORT's should be separate by comma! Ex:
    wsproxy -a 127.0.0.1:6900,127.0.0.1:6121,127.0.0.1:5121
    • Note: Use the same IP's you configured your server address at ROConfig at roBrowser.
  • -t Number of cpu cores that wsProxy should use
  • -s Enable SSL
    • -k Path to ssl key file
    • -c Path to ssl cert file
  • Use wsproxy --help for a list of available commands.

Client usage

When connecting to this websocket you will give it an IP:PORT uri, for example:

ws://websocket.example.com:5999/127.0.0.1:6900
  • You can edit allowed.js to only allow proxy to certain IP:PORT
    • Note: if you pass in the -a or --allow option when starting the wsproxy this file will be ignored.
  • We will soon release a version, with better standards for this.

Writing modules for wsProxy guidelines

  • Simply require and extend current files from the /src folder, once done, require them on wsProxy /index.js.
  • BE CAREFUL, MODULES NEED TO BE LIGHTWEIGHT, LIMIT YOURSELF TO SIMPLE I/O OPERATIONS, DON'T BLOCK, AND CREATE LITTLE GARBAGE!
  • Don't forget that node.js is single threaded, cpu intensive blocks of code will block the entire proxy!
  • Don't create to much garbage, or the garbage collector will also block for extended periods of time, thus creating "lag" for the users.

Authors

This was created for and by the roBrowser project.

Thank you

  • Einaros/ws for providing the websocket middleware