denodrivers / denodrivers/mongo
Should we deprecate this module since importing with `npm:mongodb` is working well with Deno?
- Dominant language
- TypeScript
- Stars
- 511
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
`npm:mongodb` pros:
- almost all driver features are working for me
- maintained by mongodb inc
- universal api style for both node and deno
cons:
- uses node's Buffer instead of Uint8Array
- uses node's Stream instead of async iterator and WebStream
- is not as fast as `x/mongo` because uses node compat layer
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with issue #380 and its 23-comment discussion. Compare the stated trade-offs between npm:mongodb and x/mongo, including API compatibility, performance, and Deno's Node compatibility layer. Done would require a settled decision about whether this module should be deprecated, but the payload does not identify implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, mongodb, typescript
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100