Debugging reading/writing of binary types implemented with declarative syntax is always tricky, so starting from version 2.1, jBinary allows you to see named type descriptors, structure property names and byte offsets in stack of Safari, Chrome and Firefox Developer Tools making it more meaningful so you can easily find place where [de]serializing error had occured and fix it.

Compare stack traces of error before and after this enhancement:

In conjuction with stack-displayName drop-in library it also becomes possible to see meaningful function names in Node.js stack trace: