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

protocoler

v1.0.0

Published

Utility to parse binary protocols

Downloads

6

Readme

Protocoler

An utility to parse binary protocols according to a JSON-formatted specification

Protocol specification

The protocols are defined by a JSON schema. The format of the JSON is as follows:

{
    "name": "Protocol Name",
    "version": "1.0",
    "reference": "https://url.for/documentation",
    "specList": [{
        "name": "Field Name",
        "size": 1,  // Bytes
        "values": {
            // Now list the possible values of this field. For each value, we may specify sub-fields
            "01": {
                "description": "Protocol Version",  // This value could be any string. Just using the version as an example
                // And here are the children specifications, which follows the same rules. This field is optional
                "specList": [{
                    "name": "Payload Size",
                    "size": 2,  // Again, in Bytes
                }, {
                    "name": "Payload Data",
                    "size": "Payload Size"
                    // IMPORTANT: if the size is a string, it is a reference for the value of the object with this name (in the same spec list)
                }]
            }
        }
    }, {
        "name": "Trailing value",
        "size": 1  // Again, in bytes
    }]
}

Requirements

  • ES6

How to use

let capturedSample = '0x1234';  // As example
let Protocoler = require('protocoler');

let basicSpec = {
    "name": "Basic Name",
    "version": "1.0",
    "specList": [{
        "name": "Payload",
        "size": 2  // Bytes
    }]
};

let spec = new Protocoler(basicSpec);

spec.on('value', (name, value) => {
  console.log('Found protocol item:', name, value);
});
spec.on('description', description) {
  console.log('Last value means:', description);
});
spec.on('error', err => {
  console.error('Unable to parse input data', err);
});

// Now really start parsing the hexadecimal string
spec.parseHex(capturedSample);

Current limitations (TODO's)

  • We cannot parse bit-per-bit values yet. Only bytes.
  • Values are currently only supported by hexadecimal values. (Cannot put even a string there, only a hex-representation of its bytes)