binary-packet 1.0.0

package/LICENSE

@@ -0,0 +1,61 @@
+Apache License, Version 2.0 Apache License Version 2.0, January 2004 http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
+2. Grant of Copyright License.
+
+Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License.
+
+Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
+
+4. Redistribution.
+
+You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
+
+You must give any other recipients of the Work or Derivative Works a copy of this License; and You must cause any modified files to carry prominent notices stating that You changed the files; and You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
+
+5. Submission of Contributions.
+
+Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
+
+6. Trademarks.
+
+This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty.
+
+Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability.
+
+In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability.
+
+While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS

package/README.md

@@ -0,0 +1,125 @@
+# binary-packet
+
+Lightweight and hyper-fast, zero-dependencies, TypeScript-first, schema-based binary packets serialization and deserialization library. \
+Originally made to be used for an ultrafast WebSockets communication with user-defined type-safe messages between client and server, with the smallest bytes usage possible.
+
+Supports serializing into and deserializing from [**DataView**](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DataView)s, [**ArrayBuffer**](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer)s and [**Buffer**](https://nodejs.org/api/buffer.html#buffer)s (NodeJS/Bun only). \
+To achieve the maximum performance is it always advised to use node Buffer(s) when available.
+
+## Installation
+
+Node: \
+`npm install binary-packet`
+
+Bun: \
+`bun add binary-packet`
+
+## Features & Specification
+
+Define the structure of the packets through unique Packet IDs and "schema" objects. \
+This "schema" object is simply called `Definition` and defines the shape of a packet: specifically its `fields` and their `types`.
+
+Currently, these kinds of `fields` are supported:
+| Type | Description | Values | Size (bytes) |
+|------|-------------|--------------|--------------|
+| `Field.UNSIGNED_INT_8` | 8 bits unsigned integer | 0 - 255 | 1 |
+| `Field.UNSIGNED_INT_16` | 16 bits unsigned integer | 0 - 65535 | 2 |
+| `Field.UNSIGNED_INT_32` | 32 bits unsigned integer | 0 - 4294967295 | 4 |
+| `Field.INT_8` | 8 bits signed integer | -128 - 127 | 1 |
+| `Field.INT_16` | 16 bits signed integer | -32768 - 32767 | 2 |
+| `Field.INT_32` | 32 bits signed integer | -2147483648 - 2147483647 | 4 |
+| `Field.FLOAT_32` | 32 bits IEEE754 floating-point | | 4 |
+| `Field.FLOAT_64` | 64 bits IEEE754 floating-point | | 8 |
+| `BinaryPacket` | BinaryPacket "subpacket" | BinaryPacket | size(BinaryPacket) |
+| `FieldArray` | Array of one of the types above | Up to 256 elements | 1 + length \* size(Field) |
+
+As you can see from the table above, both arrays and nested objects ("subpackets") are supported.
+
+## Usage Examples
+
+```typescript
+import { BinaryPacket, Field, FieldArray } from 'binary-packet'
+
+// Imagine we have a game board where each cell is a square and is one unit big.
+// A cell can be then defined by its X and Y coordinates.
+// For simplicity, let's say there cannot be more than 256 cells, so we can use 8 bits for each coordinate.
+const Cell = {
+  x: Field.UNSIGNED_INT_8,
+  y: Field.UNSIGNED_INT_8
+}
+
+// When done with the cell definition we can create its BinaryPacket writer/reader.
+// NOTE: each BinaryPacket needs an unique ID, for identification purposes and error checking.
+const CellPacket = BinaryPacket.define(0, Cell)
+
+// Let's now make the definition of the whole game board.
+// You can also specify arrays of both "primitive" fields and other BinaryPackets.
+const Board = {
+  numPlayers: Field.UNSIGNED_INT_8,
+  otherStuff: Field.INT_32,
+  cells: FieldArray(CellPacket) // equivalent to { cells: [CellPacket] }
+}
+
+// When done with the board definition we can create its BinaryPacket writer/reader.
+// NOTE: each BinaryPacket needs an unique ID, for identification purposes and error checking.
+const BoardPacket = BinaryPacket.define(1, Board)
+
+//////////////////
+// WRITING SIDE //
+//////////////////
+const buffer = BoardPacket.writeNodeBuffer({
+  numPlayers: 1,
+  otherStuff: 69420,
+  cells: [
+    { x: 0, y: 0 },
+    { x: 1, y: 1 }
+  ]
+})
+
+// ...
+// sendTheBufferOverTheNetwork(buffer)
+// ...
+
+//////////////////
+// READING SIDE //
+//////////////////
+import assert from 'assert'
+
+// ...
+// const buffer = receiveTheBufferFromTheNetwork()
+// ...
+
+const board = BoardPacket.readNodeBuffer(buffer)
+
+assert(board.numPlayers === 1)
+assert(board.otherStuff === 69420)
+assert(board.cells.length === 2)
+assert(board.cells[0].x === 0)
+assert(board.cells[0].y === 0)
+assert(board.cells[1].x === 1)
+assert(board.cells[1].y === 1)
+```
+
+## Benchmarks & Alternatives
+
+Benchmarks are not always meant to be taken seriously. \
+Most of the times the results of a benchmark do not actually show the full capabilities of each library. \
+So, take these "performance" comparisons with a grain of salt; or, even better, do your own benchmarks with the actual data you need to serialize/deserialize.
+
+This library has been benchmarked against the following alternatives:
+
+- [msgpackr](https://www.npmjs.com/package/msgpackr) - A very popular and very fast and battle-tested serialization library. It currently offers **many** more features than binary-packet, but it appears to be 2x-4x slower in writes and 3x-10x slower in reads.
+- [restructure](https://www.npmjs.com/package/restructure) - A very popular schema-based serialization library, has some extra features like LazyArrays, but it is **much slower** than both binary-packet and msgpackr. And, sadly, easily crashes with complex structures.
+
+The benchmarks are executed on three different kinds of packets:
+
+- EmptyPacket: basically an empty javascript object.
+- SimplePacket: objects with primitive-only fields.
+- ComplexPacket: objects with primitives, arrays and other nested objects/arrays.
+
+You can see and run the benchmarks yourself if you clone the repository and launch `npm run benchmark`.
+
+## Disclaimer
+
+This library is still very new, thus not "battle-tested" in production enough.\
+If you plan on serializing highly sensitive data or need to guarantee no crashes, use an alternative like [msgpackr](https://www.npmjs.com/package/msgpackr), or [contribute](https://github.com/silence-cloud-com/binary-packet) to this library yourself!

package/dist/index.d.mts

@@ -0,0 +1,181 @@
+declare const enum Field {
+    /**
+     * Defines a 1 byte (8 bits) unsigned integer field. \
+     * (Range: 0 - 255)
+     */
+    UNSIGNED_INT_8 = 0,
+    /**
+     * Defines a 2 bytes (16 bits) unsigned integer field. \
+     * (Range: 0 - 65535)
+     */
+    UNSIGNED_INT_16 = 1,
+    /**
+     * Defines a 4 bytes (32 bits) unsigned integer field. \
+     * (Range: 0 - 4294967295)
+     */
+    UNSIGNED_INT_32 = 2,
+    /**
+     * Defines a 1 byte (8 bits) signed integer field. \
+     * (Range: -128 - 127)
+     */
+    INT_8 = 3,
+    /**
+     * Defines a 2 bytes (16 bits) signed integer field. \
+     * (Range: -32768 - 32767)
+     */
+    INT_16 = 4,
+    /**
+     * Defines a 4 bytes (32 bits) signed integer field. \
+     * (Range: -2147483648 - 2147483647)
+     */
+    INT_32 = 5,
+    /**
+     * Defines a 4 bytes (32 bits) floating-point field. \
+     */
+    FLOAT_32 = 6,
+    /**
+     * Defines a 8 bytes (64 bits) floating-point field. \
+     */
+    FLOAT_64 = 7
+}
+/**
+ * Defines an array of a certain type. \
+ * As of now, only arrays with at most 256 elements are supported.
+ */
+declare function FieldArray<T extends Field | BinaryPacket<Definition>>(item: T): T[];
+declare class BinaryPacket<T extends Definition> {
+    private readonly packetId;
+    /**
+     * Defines a new binary packet. \
+     * Make sure that every `packetId` is unique.
+     * @throws RangeError If packetId is negative, floating-point, or greater than 255.
+     */
+    static define<T extends Definition>(packetId: number, definition?: T): BinaryPacket<T>;
+    private readonly entries;
+    readonly canFastWrite: boolean;
+    readonly minimumByteLength: number;
+    private constructor();
+    /**
+     * Reads/deserializes from the given Buffer. \
+     * Method available ONLY on NodeJS and Bun.
+     *
+     * If possible, always prefer reading using this method, as it is much faster than the other ones.
+     *
+     * NOTE: if you have an ArrayBuffer do not bother wrapping it into a node Buffer yourself. \
+     * NOTE: if you have an ArrayBuffer use the appropriate `readArrayBuffer`.
+     */
+    readNodeBuffer(dataIn: Buffer, offsetPointer?: {
+        offset: number;
+    }, byteLength?: number): ToJson<T>;
+    /**
+     * Reads/deserializes from the given DataView.
+     *
+     * NOTE: if you have an ArrayBuffer do not bother wrapping it into a DataView yourself. \
+     * NOTE: if you have an ArrayBuffer use the appropriate `readArrayBuffer`.
+     */
+    readDataView(dataIn: DataView, offsetPointer?: {
+        offset: number;
+    }, byteLength?: number): ToJson<T>;
+    /**
+     * Reads/deserializes from the given ArrayBuffer. \
+     * WARNING: this method is practically a HACK.
+     *
+     * When using this method both the `byteOffset` and `byteLength` are REQUIRED and cannot be defaulted. \
+     * This is to prevent serious bugs and security issues. \
+     * That is because often raw ArrayBuffers come from a pre-allocated buffer pool and do not start at byteOffset 0.
+     *
+     * NOTE: if you have a node Buffer do not bother wrapping it into an ArrayBuffer yourself. \
+     * NOTE: if you have a node Buffer use the appropriate `readNodeBuffer` as it is much faster and less error prone.
+     */
+    readArrayBuffer(dataIn: ArrayBuffer & {
+        buffer?: undefined;
+    }, byteOffset: number, byteLength: number): ToJson<T>;
+    /**
+     * Writes/serializes the given object into a Buffer. \
+     * Method available ONLY on NodeJS and Bun.
+     *
+     * If possible, always prefer writing using this method, as it is much faster than the other ones.
+     */
+    writeNodeBuffer(dataOut: ToJson<T>): Buffer;
+    /**
+     * Writes/serializes the given object into a DataView. \
+     */
+    writeDataView(dataOut: ToJson<T>): DataView;
+    /**
+     * Writes/serializes the given object into an ArrayBuffer. \
+     * This method is just a wrapper around either  `writeNodeBuffer` or `writeDataView`. \
+     *
+     * This method works with JavaScript standard raw ArrayBuffer(s) and, as such, is very error prone: \
+     * Make sure you're using the returned byteLength and byteOffset fields in the read counterpart. \
+     *
+     * Always consider whether is possible to use directly `writeNodeBuffer` or `writeDataView` instead of `writeArrayBuffer`. \
+     * For more information read the `readArrayBuffer` documentation.
+     */
+    writeArrayBuffer(dataOut: ToJson<T>): {
+        buffer: ArrayBufferLike;
+        byteLength: number;
+        byteOffset: number;
+    };
+    private read;
+    private write;
+    private fastWrite;
+    /**
+     * The slow writing path tries writing data into the buffer as fast as the fast writing path does. \
+     * But, if a non-empty array is encountered, the buffer needs to grow, slightly reducing performance.
+     */
+    private slowWrite;
+}
+/**
+ * BinaryPacket definition: \
+ * Any packet can be defined through a "schema" object explaining its fields names and types.
+ *
+ * @example
+ * // Imagine we have a game board where each cell is a square and is one unit big.
+ * // A cell can be then defined by its X and Y coordinates.
+ * // For simplicity, let's say there cannot be more than 256 cells, so we can use 8 bits for each coordinate.
+ * const Cell = {
+ *  x: Field.UNSIGNED_INT_8,
+ *  y: Field.UNSIGNED_INT_8
+ * }
+ *
+ * // When done with the cell definition we can create its BinaryPacket writer/reader.
+ * // NOTE: each BinaryPacket needs an unique ID, for identification purposes and error checking.
+ * const CellPacket = BinaryPacket.define(0, Cell)
+ *
+ * // Let's now make the definition of the whole game board.
+ * // You can also specify arrays of both "primitive" fields and other BinaryPackets.
+ * const Board = {
+ *  numPlayers: Field.UNSIGNED_INT_8,
+ *  cells: FieldArray(CellPacket) // equivalent to { cells: [CellPacket] }
+ * }
+ *
+ * // When done with the board definition we can create its BinaryPacket writer/reader.
+ * // NOTE: each BinaryPacket needs an unique ID, for identification purposes and error checking.
+ * const BoardPacket = BinaryPacket.define(1, Board)
+ *
+ * // And use it.
+ * const buffer = BoardPacket.writeNodeBuffer({
+ *  numPlayers: 1,
+ *  cells: [
+ *    { x: 0, y: 0 },
+ *    { x: 1, y: 1 }
+ *  ]
+ * })
+ *
+ * // sendTheBufferOver(buffer)
+ * // ...
+ * // const buffer = receiveTheBuffer()
+ * const board = BoardPacket.readNodeBuffer(buffer)
+ * // ...
+ */
+type Definition = {
+    [fieldName: string]: Field | Field[] | BinaryPacket<Definition> | BinaryPacket<Definition>[];
+};
+/**
+ * Meta-type that converts a `Definition` schema to the type of the actual JavaScript object that will be written into a packet or read from. \
+ */
+type ToJson<T extends Definition> = {
+    [K in keyof T]: T[K] extends ReadonlyArray<infer Item> ? Item extends BinaryPacket<infer BPDef> ? ToJson<BPDef>[] : number[] : T[K] extends BinaryPacket<infer BPDef> ? ToJson<BPDef> : number;
+};
+
+export { BinaryPacket, type Definition, Field, FieldArray };

package/dist/index.d.ts

@@ -0,0 +1,181 @@
+declare const enum Field {
+    /**
+     * Defines a 1 byte (8 bits) unsigned integer field. \
+     * (Range: 0 - 255)
+     */
+    UNSIGNED_INT_8 = 0,
+    /**
+     * Defines a 2 bytes (16 bits) unsigned integer field. \
+     * (Range: 0 - 65535)
+     */
+    UNSIGNED_INT_16 = 1,
+    /**
+     * Defines a 4 bytes (32 bits) unsigned integer field. \
+     * (Range: 0 - 4294967295)
+     */
+    UNSIGNED_INT_32 = 2,
+    /**
+     * Defines a 1 byte (8 bits) signed integer field. \
+     * (Range: -128 - 127)
+     */
+    INT_8 = 3,
+    /**
+     * Defines a 2 bytes (16 bits) signed integer field. \
+     * (Range: -32768 - 32767)
+     */
+    INT_16 = 4,
+    /**
+     * Defines a 4 bytes (32 bits) signed integer field. \
+     * (Range: -2147483648 - 2147483647)
+     */
+    INT_32 = 5,
+    /**
+     * Defines a 4 bytes (32 bits) floating-point field. \
+     */
+    FLOAT_32 = 6,
+    /**
+     * Defines a 8 bytes (64 bits) floating-point field. \
+     */
+    FLOAT_64 = 7
+}
+/**
+ * Defines an array of a certain type. \
+ * As of now, only arrays with at most 256 elements are supported.
+ */
+declare function FieldArray<T extends Field | BinaryPacket<Definition>>(item: T): T[];
+declare class BinaryPacket<T extends Definition> {
+    private readonly packetId;
+    /**
+     * Defines a new binary packet. \
+     * Make sure that every `packetId` is unique.
+     * @throws RangeError If packetId is negative, floating-point, or greater than 255.
+     */
+    static define<T extends Definition>(packetId: number, definition?: T): BinaryPacket<T>;
+    private readonly entries;
+    readonly canFastWrite: boolean;
+    readonly minimumByteLength: number;
+    private constructor();
+    /**
+     * Reads/deserializes from the given Buffer. \
+     * Method available ONLY on NodeJS and Bun.
+     *
+     * If possible, always prefer reading using this method, as it is much faster than the other ones.
+     *
+     * NOTE: if you have an ArrayBuffer do not bother wrapping it into a node Buffer yourself. \
+     * NOTE: if you have an ArrayBuffer use the appropriate `readArrayBuffer`.
+     */
+    readNodeBuffer(dataIn: Buffer, offsetPointer?: {
+        offset: number;
+    }, byteLength?: number): ToJson<T>;
+    /**
+     * Reads/deserializes from the given DataView.
+     *
+     * NOTE: if you have an ArrayBuffer do not bother wrapping it into a DataView yourself. \
+     * NOTE: if you have an ArrayBuffer use the appropriate `readArrayBuffer`.
+     */
+    readDataView(dataIn: DataView, offsetPointer?: {
+        offset: number;
+    }, byteLength?: number): ToJson<T>;
+    /**
+     * Reads/deserializes from the given ArrayBuffer. \
+     * WARNING: this method is practically a HACK.
+     *
+     * When using this method both the `byteOffset` and `byteLength` are REQUIRED and cannot be defaulted. \
+     * This is to prevent serious bugs and security issues. \
+     * That is because often raw ArrayBuffers come from a pre-allocated buffer pool and do not start at byteOffset 0.
+     *
+     * NOTE: if you have a node Buffer do not bother wrapping it into an ArrayBuffer yourself. \
+     * NOTE: if you have a node Buffer use the appropriate `readNodeBuffer` as it is much faster and less error prone.
+     */
+    readArrayBuffer(dataIn: ArrayBuffer & {
+        buffer?: undefined;
+    }, byteOffset: number, byteLength: number): ToJson<T>;
+    /**
+     * Writes/serializes the given object into a Buffer. \
+     * Method available ONLY on NodeJS and Bun.
+     *
+     * If possible, always prefer writing using this method, as it is much faster than the other ones.
+     */
+    writeNodeBuffer(dataOut: ToJson<T>): Buffer;
+    /**
+     * Writes/serializes the given object into a DataView. \
+     */
+    writeDataView(dataOut: ToJson<T>): DataView;
+    /**
+     * Writes/serializes the given object into an ArrayBuffer. \
+     * This method is just a wrapper around either  `writeNodeBuffer` or `writeDataView`. \
+     *
+     * This method works with JavaScript standard raw ArrayBuffer(s) and, as such, is very error prone: \
+     * Make sure you're using the returned byteLength and byteOffset fields in the read counterpart. \
+     *
+     * Always consider whether is possible to use directly `writeNodeBuffer` or `writeDataView` instead of `writeArrayBuffer`. \
+     * For more information read the `readArrayBuffer` documentation.
+     */
+    writeArrayBuffer(dataOut: ToJson<T>): {
+        buffer: ArrayBufferLike;
+        byteLength: number;
+        byteOffset: number;
+    };
+    private read;
+    private write;
+    private fastWrite;
+    /**
+     * The slow writing path tries writing data into the buffer as fast as the fast writing path does. \
+     * But, if a non-empty array is encountered, the buffer needs to grow, slightly reducing performance.
+     */
+    private slowWrite;
+}
+/**
+ * BinaryPacket definition: \
+ * Any packet can be defined through a "schema" object explaining its fields names and types.
+ *
+ * @example
+ * // Imagine we have a game board where each cell is a square and is one unit big.
+ * // A cell can be then defined by its X and Y coordinates.
+ * // For simplicity, let's say there cannot be more than 256 cells, so we can use 8 bits for each coordinate.
+ * const Cell = {
+ *  x: Field.UNSIGNED_INT_8,
+ *  y: Field.UNSIGNED_INT_8
+ * }
+ *
+ * // When done with the cell definition we can create its BinaryPacket writer/reader.
+ * // NOTE: each BinaryPacket needs an unique ID, for identification purposes and error checking.
+ * const CellPacket = BinaryPacket.define(0, Cell)
+ *
+ * // Let's now make the definition of the whole game board.
+ * // You can also specify arrays of both "primitive" fields and other BinaryPackets.
+ * const Board = {
+ *  numPlayers: Field.UNSIGNED_INT_8,
+ *  cells: FieldArray(CellPacket) // equivalent to { cells: [CellPacket] }
+ * }
+ *
+ * // When done with the board definition we can create its BinaryPacket writer/reader.
+ * // NOTE: each BinaryPacket needs an unique ID, for identification purposes and error checking.
+ * const BoardPacket = BinaryPacket.define(1, Board)
+ *
+ * // And use it.
+ * const buffer = BoardPacket.writeNodeBuffer({
+ *  numPlayers: 1,
+ *  cells: [
+ *    { x: 0, y: 0 },
+ *    { x: 1, y: 1 }
+ *  ]
+ * })
+ *
+ * // sendTheBufferOver(buffer)
+ * // ...
+ * // const buffer = receiveTheBuffer()
+ * const board = BoardPacket.readNodeBuffer(buffer)
+ * // ...
+ */
+type Definition = {
+    [fieldName: string]: Field | Field[] | BinaryPacket<Definition> | BinaryPacket<Definition>[];
+};
+/**
+ * Meta-type that converts a `Definition` schema to the type of the actual JavaScript object that will be written into a packet or read from. \
+ */
+type ToJson<T extends Definition> = {
+    [K in keyof T]: T[K] extends ReadonlyArray<infer Item> ? Item extends BinaryPacket<infer BPDef> ? ToJson<BPDef>[] : number[] : T[K] extends BinaryPacket<infer BPDef> ? ToJson<BPDef> : number;
+};
+
+export { BinaryPacket, type Definition, Field, FieldArray };