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

gotti-colyseus

v0.1.0

Published

So I started off trying to just alter the colyseus code, but after a couple days of that, I realized it was stupid and I should stop trying to fit all my edge cases into colyseus because at the end of the day what I'm trying to build is different enough t

Downloads

8

Readme

So I started off trying to just alter the colyseus code, but after a couple days of that, I realized it was stupid and I should stop trying to fit all my edge cases into colyseus because at the end of the day what I'm trying to build is different enough that I was wasting too much time trying to make things work with the already existing colyseus engine. On top of that, if things change in colyseus they could break my engine.

SO

I basically decided to start with a blank project, and from the ground up I'm going to take bits from the colyseus engine and implement them to fit my distributed messaging engine (gotti-channels).

So far i've made decent progress. The protocols are all completely different and I'm still figuring out some kinks for clients listening/writing to different areas. Right now you can send a request and then basically return options/true or anything truthy for it to be success, and return something falsey for it to be rejected.

This will be ironed out as I continue to develop the API.

I plan on building this around my Gotti.js project which will be using a system message queue on both client and server side.

Therefore I'm implementing messaging protocols to fulfil the needs of remote/local/global/client/etc etc messaging to and from different systems.