I thought this was a problem with v2.0.3 but it seems to just be a bug. The raw numbers were not behaving as expected causing an out of bounds value when trying to use buff.writeUInt32LE.
The current code still cannot handle a uint64 number with full precision it seems but numbers larger than a uint32 no longer make it barf.
I thought this was a problem with v2.0.3 but it seems to just be a bug. The raw numbers were not behaving as expected causing an out of bounds value when trying to use buff.writeUInt32LE.
The current code still cannot handle a uint64 number with full precision it seems but numbers larger than a uint32 no longer make it barf.