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

wse-cc

v3.0.8

Published

Manual multi-server client/instance management. If nothing else helped.

Downloads

17

Readme

WSE + Cross-server Controller

Cheap and simple node.js ws ballancer/controller with ability to communicate between server instances. It allows to start instances on a different physical servers, if you want.

Look at wse before you start.

Why?

If you need to manage your clients between your servers or game instances with some very specific rules and without any extra-layers or load ballancers.

Components

  • master - Main process with known host/port. used as registry of existing users.

  • demon - Service process. It always running on some server. Usually only responsive for starting child processes - cores.

  • core - Child process. It can be chat room, level, or game session. When core started – it also starting with websocket server on port, that automatically selected by demon before. And demon also report about this host/port to master. So, master know how user can connect to each core. Demon start cores, when master ask for it.

How exactly?

There is a simple example inside /example folder. But there is no client example yet. There is an example + vue template but it's might be outdated.

I'm not bothering with docs too much, as this package not used by anyone but me yet :)

If you need any help: ping me on twitter or github. Will be happy to help.