Releases: share/sharedb-mongo
Releases · share/sharedb-mongo
v5.0.0
v4.2.0
- #157 (@alecgibson) — Allow disabling the
src
/seq
/v
index: to be used in conjunction with[email protected]
, which tries to avoid hitting this index. The index can be opted out of with:
new ShareDbMongo(
mongoUrl,
{
disableIndexCreation: {
src_seq_v: true,
},
},
);
Existing indexes will need to be manually deleted if they're no longer desired.
Note that it's technically still possible to try to look documents up by src
/seq
/v
. The chance should be remote, but it's not impossible. Removing this index may lead to very bad performance in these corner cases.
v4.1.2
- Add
sharedb@5
support
v4.1.1
What's Changed
- Fix
$map
query transform by @ericyhwang in #154- It would just hang previously. It's very likely unused by any consumers, but it's not much code to keep support for it.
- Resolve memory leak when using cursor operations like
$count
in mongodb@4-6 by @ericyhwang in #152- This mostly affected
$count
.$explain
was affected as well, though that usually won't be used in a production service. ⚠️ If you also use the Mongo Node driver directly:- Be warned that, while this patches the memory leak when using sharedb-mongo, directly using the underlying Node driver can still leak sessions when using
cursor.count()
orcursor.explain()
. - On Mongo's end, it's tracked in https://jira.mongodb.org/browse/NODE-4833 and https://jira.mongodb.org/browse/NODE-4845.
- Be warned that, while this patches the memory leak when using sharedb-mongo, directly using the underlying Node driver can still leak sessions when using
- Thanks to @deongroenewald for the report and repro case!
- This mostly affected
Full Changelog: v4.1.0...v4.1.1
v4.1.0
v4.0.0
What's Changed
Note - This release has no actual breaking changes since sharedb@3, so if you are not using Node 14 any longer, it's safe to do a drop-in upgrade.
- 💥 Drop Node.js 14 and add Node.js 20 by @alecgibson in #148
- Add support for sharedb@4 by @ericyhwang in #149
Full Changelog: v3.0.1...v4.0.0