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

binary-decoder

v0.6.2

Published

Decoder for complex binary data

Downloads

86

Readme

binary-decoder 0.6.2

Decoder for structure binary data

pipeline status binary-decoder on NPM license developtment time contributor covenant support development

Decoder module for decoding binary data that has a structured but variable structure. The structure of the data is specified using an array of data parts.

Data Types

byte, uint8, int8, uint16, int16, uint32, int32

An integer

Options

  • id ID of field (will be used as the key in the output object)
  • littleEndian If true, will decode as littleEndian
  • partial If true, the nextByte counter that tracks the current position in the data will not be progressed.

bytes

An custom byte-length integer

Options

  • id ID of field (will be used as the key in the output object)
  • littleEndian If true, will decode as littleEndian
  • partial If true, the nextByte counter that tracks the current position in the data will not be progressed.

bits

Bit-size structured data. Must total a number of bytes.

Options

  • id ID of field (will be used as the key in the output object). If not given, bit values will be set in containing object.
  • parts Bit parts that make up the data
  • partial If true, the nextByte counter that tracks the current position in the data will not be progressed. This is useful for using a map based on the first x-bits of a byte when the map includes the remaining bits in the byte

bitsInt

Integer spread across multiple, separated bits

Options

  • id ID of field (will be used as the key in the output object)
  • bits Bits to skip/take in an alternating fashion e.g. [0, 5, 3, 5, 3, 8] will be an 16-bit integer from 3 bytes, bits8:4 of the first byte, bits 8:4 of the second and the full last byte
  • partial If true, the nextByte counter that tracks the current position in the data will not be progressed. This is useful for using a map based on the first x-bits of a byte when the map includes the remaining bits in the byte

variable

Variable-length number

Options

  • id ID of field (will be used as the key in the output object)
  • length Length or key to value of length of data

string

String. If a NULL character (\0) is encountered, the string will be terminated and the rest of the bytes will be discarded unless the noDiscard option is set.

Options

  • id ID of field (will be used as the key in the output object)
  • length Length or key to value of length of string

repeat

n-parts of structured data

Options

  • id ID of field (will be used as the key in the output object)
  • repeats Number of parts
  • asArray Store parts in an array
  • asObject Store the parts in an object using the value for the given key as the part's key in the object

map

Data that can be any of a given number of structures

Options

  • id ID of field (will be used as the key in the output object)
  • key Key to value to determine structure of data
  • structures Object of value/structure of the possible data structures

Example

import { readFile } from 'fs/promises';
import { createDecoder } from 'binary-decoder';
import structure from './structure.js';

const decoder = createDecoder(structure, {
  littleEndian: false,
  throwOnInvalidEnumValue: true,
  logger: {
    debug: (...args) => console.debug(...args)
  }
});

const { nextByte, decodedMessage } = decoder.decode(new Uint8Array(await readFile('data.bin')));

console.log(decodedMessage);

structure.js

/** @type {import('binary-decoder').MessageStructure} */
export default [
  {
    type: 'uint16',
    id: 'messageLength'
  },
  {
    type: 'repeat',
    id: 'data',
    asObject: 'type',
    structure: [
      {
        type: 'byte',
        id: 'type',
        enums: [
          {
            value: 1,
            label: 'Header',
            key: 'header'
          },
          {
            value: 2,
            label: 'Payload',
            key: 'payload'
          }
        ]
      },
      {
        type: 'map',
        key: 'type',
        structures: {
          1: [
            {
              type: 'uint8',
              id: 'idLength'
            },
            {
              type: 'string',
              id: 'id',
              length: 'idLength'
            }
          ],
          2: [
            {
              type: 'uint16',
              id: 'payloadLength'
            },
            {
              type: 'variable',
              id: 'payload',
              length: 'payloadLength'
            }
          ]
        }
      }
    ]
  }
];

Development

Feel free to post errors or feature requests to the project issue tracker or email them to us. Please submit security concerns as a confidential issue

The source is hosted on Gitlab and uses prettier, lint-staged and husky to keep things pretty. As such, when you first clone the repository, as well as installing the npm dependencies, you will also need to install husky.

# Install NPM dependencies
npm install
# Set up husky Git hooks stored in .husky
npx husky install

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

[0.6.2] - 2024-05-14

Fixed

  • Fixed handling of 4 byte integers

0.6.1 - 2023-03-04

Fixed

  • Log level of initial log message

0.6.0 - 2022-12-21

Changed

  • Allowed bits values to be stored in an object using the id parameter

0.5.0 - 2022-08-05

Changed

  • If a NULL character \0 is encountered in a string, the string will be terminated and the rest of the bytes of the string will be discarded unless the noDiscard option is set

0.4.0 - 2022-07-25

Added

  • bitsInt for integers spread across multiple bytes with bits that should be ignored

0.3.0 - 2022-06-16

Fixed

  • Breaking Corrects mapping of enums for integer types (byte, uint8 etc).

    This will break functionality if you were using the incorrect key of enum (instead of enums) for the enums array. enums is used instead of enum as enum is a reserved word in JavaScript/ECMAScript.

0.2.0 - 2022-06-16

Added

  • partial flag to bits type adding the ability to use a map from an key value smaller than a byte
  • Handling of multi-byte bit ranges
  • Throw error on not enough data

0.1.0 - 2022-06-15

Initial version!