You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of version 5.0.0, the official mongo nodejs driver supports only promises. Given that the original purpose of this library was to add a promise-compatible interface for the native driver, I think mongoist is no longer useful. Anyone who'd like a promise-compatible api, should just use the native driver.
As a result, I'm proposing adding a notice to the readme and archiving this repo. As it is, the package is pretty out of date and no longer really useful for modern node/mongodb projects.
The text was updated successfully, but these errors were encountered:
I believe what you are trying to say is that the official driver doesn't support callbacks anymore?
Farewell to Callbacks
Most notably, we have removed support for callbacks in favor of a Promise-only public API.
Other than that, I'm not super familiar with either library, but I believe Mongoist still brings some stuff to the game that the official driver doesn't, like for example access to collections in a different way.
The original purpose of this library was to promisify the mongo driver's API (that's why I started maintaining it originally). As you said, the official driver supports promises natively now. As such, I don't think there's a reason to continue maintaining the library and folks should migrate off it.
As of version 5.0.0, the official mongo nodejs driver supports only promises. Given that the original purpose of this library was to add a promise-compatible interface for the native driver, I think
mongoist
is no longer useful. Anyone who'd like a promise-compatible api, should just use the native driver.As a result, I'm proposing adding a notice to the readme and archiving this repo. As it is, the package is pretty out of date and no longer really useful for modern node/mongodb projects.
The text was updated successfully, but these errors were encountered: