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

wsbitpacket

v1.0.6

Published

A websocket networking library to easily packet messages into its smallest binary format.

Downloads

4

Readme

wsbitpacket

Welcome to wsbitpacket, a fast, reliable, and simple way to send binary packets between server and client via websockets.

Installation

npm install wsbitpacket

Binary Types Support

| Type | Range | | --------- | ------------------------------ | | Uint8 | 0 - 255 | | Uint16 | 0 - 65,535 | | Uint24 | 0 - 16,777,215 | | Uint32 | 0 - 4,294,967,295 | | Int8 | -128 - 127 | | Int16 | -32,768 - 32,767 | | Int24 | -8,388,608 - 8,388,607 | | Int32 | -2,147,483,648 - 2,147,483,647 | | BigInt64 | really big +/- | | BigUint64 | even bigger +/- | | Float32 | 4 bytes of decimal | | Float64 | 8 bytes of decimal | | String | unicode char 0-255 any length |

How does it work?

Server.js

import bitpacket from 'wsbitpacket';

const PORT = process.env.PORT || 3000;

// Define how your packets will look
const schemas = new bitpacket.BitSchema(
    // Server schemas
    [
        { name: 'playerUpdate', data: { id: bitpacket.BinaryTypes.Uint8, x: bitpacket.BinaryTypes.Uint16, y: bitpacket.BinaryTypes.Uint16 } },
        { name: 'healthUpdate', data: { health: bitpacket.BinaryTypes.Uint8 } },
    ],
    // Client Schemas
    [
        { name: 'mousemove', data: { angle: bitpacket.BinaryTypes.Uint8 } },
        { name: 'chat', data: { message: bitpacket.BinaryTypes.String } },
        { name: 'bigNumber', data: { number: bitpacket.BinaryTypes.BigUint64 } },
    ]
);

const server = new bitpacket.Server(PORT, schemas);

// A client connects to the websocket
server.onConnection((socket, req) => {
    socket.on('disconnect', () => {
        // client disconnected
    });

    socket.on('mousemove', data => {
        // server receives a message from the client based on the client-send schemas^
        // data: { angle: 49 }
    });
    socket.on('bigNumber', data => {
        // data: {number: 9999999999999999999n }
    });

    // Server sends a message to the client based on the server-send schemas^
    socket.send('playerUpdate', {
        id: 63,
        x: 9999,
        y: 5493,
    });
});

Client.js

import bitpacket from 'wsbitpacket';

const PORT = 3000;

const client = new bitpacket.Client(`ws://localhost:${PORT}`);

client.on('connection', () => {
    // send a packet to the server based on how you defined your client-send schemas^
    client.send('mousemove', {
        angle: 49,
    });
    client.send('bigNumber', {
        // when sending BigUint64 or BigInt64 make sure to put an "n" at the end of the numebr
        // or wrap it in BigInt()
        number: 9999999999999999999n,
    });
    // disconnect from the server
    client.disconnect();
});

client.on('disconnect', () => {
    // the client has disconnected from the server
});

// Fired when the server sends you an update, in this case, playerUpdate
client.on('playerUpdate', data => {
    // data: { id: 63, x: 9999, y: 5493 }
});

Contribute

Found a problem or want to contrubute? Fork this repository and leave pull request

MIT License