buffer 4.9.1 can cause errors #93

Borewit · 2019-08-11T07:47:28Z

Calling a read function on the embedded buffer without any argument will throw an exception.
This is major incompatibility issue with node.js buffer.

Error message thrown: "RangeError: offset is not uint"

Corresponding issue: feross/buffer#237

I suggest to reconsider PR: #68, which does fix the issue

…rors webpack/node-libs-browser#93 Webpack 4 now is a stable version. It uses node-libs for Buffer polyfill that is not completely compatible with the nodejs implemintation. In node-libs a lot of optional arguments are required, so we get an offset error in the browser calling buffer.readUInt32BE without an argument.

Borewit mentioned this issue Aug 11, 2019

RangeError: offset is not uint tulios/kafkajs#311

Closed

ortexx mentioned this issue Sep 21, 2020

Passed arguments everywhere to buffer.readUInt32BE() to avoid some errors Zazama/node-id3#81

Merged

Sajjon mentioned this issue Jun 28, 2021

missing param for hw sign radixdlt/radixdlt-javascript#149

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

buffer 4.9.1 can cause errors #93

buffer 4.9.1 can cause errors #93

Borewit commented Aug 11, 2019 •

edited

Loading

buffer 4.9.1 can cause errors #93

buffer 4.9.1 can cause errors #93

Comments

Borewit commented Aug 11, 2019 • edited Loading

Borewit commented Aug 11, 2019 •

edited

Loading