-
Notifications
You must be signed in to change notification settings - Fork 29
🛠️ Replace deprecated Buffer() constructor with Buffer.from() for compatibility and security
#37
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
Conversation
|
@csquared Let me know if anything’s needed from my side. |
|
Thanks for the catch! |
|
looks like some issues in the integration tests - I'm sure those have suffered from some bitrot. Any chance you'd want to take a crack at those :D ? |
Yeah, I'll take a look and patch up the integration tests. |
@csquared done. |
|
Nice work! Once the integration tests are passing I'm going to merge this and another PR I've been sitting on. |
|
@stephinson thank you! |
|
version 0.3.3 released last night |
This pull request addresses the deprecation of the
Buffer()constructor in Node.js by replacing it withBuffer.from(). TheBuffer()constructor has been deprecated due to security and usability issues. UsingBuffer.from()ensures compatibility with current Node.js versions and adheres to best practices for buffer creation.Additionally, this update includes:
Merging this pull request will eliminate deprecation warnings related to
Buffer()usage.