max-mapper / max-mapper/concat-stream
Buffer constructor runtime deprecation - this package emits a warning on Node 10
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 574
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
Hey from Node.js here!,
Starting on Node 10 this package will emit deprecation warnings. See this guide on what you should do in order to migrate to Buffer.alloc/Buffer.from.
See https://github.com/nodejs/node/issues/19079 for discussion around this change and why we can't make new Buffer work
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by locating Buffer constructor uses in the package and read the linked safer-buffer migration guide; done means replacing the deprecated usage with the appropriate Buffer.alloc or Buffer.from form and confirming the package no longer emits the Node 10 deprecation warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100