deprecate buffer-fill
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
`Buffer.fill` exist natively now and for a long time.
- [ ] Update the readme with examples how to use built
- [ ] Update readme and recommend using just plain vanilla `new ArrayBuffer()` or `new Uint8array()` instead that is more cross env friendly
- [ ] Mark the npm package as deprecated (not needed anymore)
- [ ] archive the githup repo?
ppl should stop using a legacy node version that don't get any more updates
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
Start with the repository README and the package's npm listing. Update the examples and recommendation to use native Buffer.fill and the mentioned ArrayBuffer or Uint8Array alternatives, then mark the package deprecated; repository archiving is also listed for consideration. Done means the README and npm package clearly direct users away from this legacy package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- documentation, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100