New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calling readUInt32LE with no arguments throws an exception in buffer v4 #237
Comments
It's ridiculous that they won't update to the latest Cheers! |
The old version of `buffer` that webpack bundled has a bug causing sample to fail. feross/buffer#237 This PR upgrades webpack to v5 and adds required polyfills as in v5 they are no longer built-in.
The old version of `buffer` that webpack bundled has a bug causing sample to fail. feross/buffer#237 This PR upgrades webpack to v5 and adds required polyfills as in v5 they are no longer built-in.
The old version of `buffer` that webpack bundled has a bug causing sample to fail. feross/buffer#237 This PR upgrades webpack to v5 and adds required polyfills as in v5 they are no longer built-in.
The old version of `buffer` that webpack bundled has a bug causing sample to fail. feross/buffer#237 This PR upgrades webpack to v5 and adds required polyfills as in v5 they are no longer built-in.
Issue on buffer: 4.9.1.
Expected behaviour:
Call
buffer.readUInt32LE()
will read a 32-bit unsigned integer from the buffer start at position since this is how node.js buffer behaves.Actual behaviour:
Throws an exception: "RangeError: offset is not uint"
There are likely other read function behaving the same. But this specific one, was an issue for me.
Although this issue is already fixed in v5, webpack v4 which relying on node-libs-browser, which is relying on buffer 4.9.1 and does not want to update to v5 for good or bad reasons.
Related issues:
Do you think it is worth releasing a 4.9 patch @feross?
The text was updated successfully, but these errors were encountered: