binary-parser icon indicating copy to clipboard operation
binary-parser copied to clipboard

Blazing-fast declarative binary parser builder for node.js

Results 7 binary-parser issues
Sort by recently updated
recently updated
newest added

Hello! This is to fix a simple problem: I can't compile the project without the context.d.ts file being added to npm. I took some liberty to also run the audit...

Documentation says: `Encoded result will be returned as a Buffer object.` Parser.encode() is declared as `encode(obj: any): any;` in binary_parser.d.ts Parser.encode() return type should be declared as Buffer

![image](https://user-images.githubusercontent.com/6687517/100562531-0541b500-328a-11eb-9f13-25a5c2fb80de.png) This is the error I get! This library as well as keichi's one worked before, but now they both don't! going back to the previous version it remains broken,...

This change could possibly be breaking. Another way to do it would be wrap the return value into another object. ``` return { bytesRead: offset, vars} ``` But that 100%...

Hi @Ericbla, I forked your binary-parser-encoder fork and updated it by cherry picking all the commits from the original project that were missing here. I also got all current tests...

If i use bit fields the are always serialized in big endian order, but the encoder seems to respect the endianess set for the parser. The result is only bigendian...