Time to deprecated the npm package?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
`Buffer.alloc` 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 by reviewing the README and the package's current npm and GitHub status. The requested outcome includes documenting native alternatives, marking the npm package deprecated, and deciding whether to archive the repository, but the issue does not define the examples or the archival decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- documentation, release, tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100