A high-level JavaScript API for creating, loading, parsing, modifying, and saving complex binary files and data structures.
jBinary is a high-level JavaScript API designed to simplify working with binary data. It allows developers to create, load, parse, modify, and save complex binary files and data structures using declarative type definitions. The library abstracts low-level binary operations, enabling manipulation of binary data as native JavaScript objects.
JavaScript developers working with binary file formats, such as archives (e.g., TAR), media streams (e.g., MPEG-TS), or game assets, in both browser and Node.js environments.
Developers choose jBinary for its declarative approach to binary data, which reduces complexity and boilerplate code. It provides a unified, high-level API that works across platforms, making it easier to handle diverse binary formats without dealing with raw byte-level operations.
High-level API for working with binary data.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables defining complex binary structures with JavaScript-like syntax and automatic type caching, as shown in the TAR archive example where files are manipulated as objects.
Works seamlessly in browsers and Node.js by building on jDataView, a DataView polyfill with extensions, ensuring consistent behavior across environments.
Allows reading, writing, and modifying binary data as native JavaScript objects, abstracting low-level byte operations and reducing boilerplate code.
Includes examples and typesets for practical formats like TAR archives and MPEG-TS, demonstrated in demos such as the Apple HTTP Live Streaming player.
Relies on jDataView for browser compatibility, which can add performance overhead and complexity compared to native DataView or Buffer APIs in modern environments.
Has fewer out-of-the-box format parsers than more established libraries, as noted in the jBinary.Repo, requiring custom development for unsupported formats.
API documentation is spread across a wiki, which may be less maintained and harder to navigate compared to integrated docs, potentially slowing onboarding.