Skip to content

Releases: mongodb/node-mongodb-native

v4.0.0-beta.6

01 Jul 17:00
@nbbeeken nbbeeken
v4.0.0-beta.6
a4e14ff
This commit was signed with the committer’s verified signature.
nbbeeken Neal Beeken
GPG key ID: 22F3C38EA1A0C076
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.0.0-beta.6 Pre-release
Pre-release

The MongoDB Node.js team is pleased to announce version 4.0.0-beta.6 of the mongodb package!

Release Highlights

This is on the larger side of the beta releases we've done so far we're getting closer to calling this version official.

As a breaking change in this release we now make use of the new MongoDriverError and MongoServerError to clarify where the issue arose from. All of the errors that our driver throws subclass from MongoError so its possible to filter in catch blocks using instanceof. Take a look at this example:

// without calling .connect()
await c.insertOne({ a: 1 })
// Uncaught MongoDriverError: MongoClient must be connected before calling MongoClient.prototype.db
//   at MongoClient.db (lib/mongo_client.js)
await c.insertOne({ _id: /a/ })
// Uncaught MongoServerError: can't use a regex for _id
//   at lib/operations/insert.js {
//     index: 0,
//     code: 2
//   }

Here's the highlights:

  • BSON-EXT support is back! Make sure you use bson-ext v4 with the driver v4.
  • Our typescript got some big upgrades, you should get hinting and completion for filters in .find() and update specifiers in findOneAndUpdate()
  • If you store regular expressions in mongodb from another language where the symbols are not supported in native JS regexes, you can now set the bsonRegExp flag to retrieve them
   await collection.insertOne({ a: new BSONRegExp('(?-i)AA_') })
   await collection.findOne({ a: new BSONRegExp('(?-i)AA_') }, { bsonRegExp: true })
   // { _id: ObjectId,  a: BSONRegExp { pattern: '(?-i)AA_', options: '' } }

⚠ BREAKING CHANGES

Features

Bug Fixes

Documentation

We invite you to try the mongodb library immediately, and report any issues to the NODE project.

Loading

v4.0.0-beta.5

26 May 21:53
@dariakp dariakp
v4.0.0-beta.5
f066b13
This commit was signed with the committer’s verified signature.
dariakp Daria Pardue
GPG key ID: A686E99780FAD44A
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.0.0-beta.5 Pre-release
Pre-release

The MongoDB Node.js team is pleased to announce version 4.0.0-beta.5 of the driver!

Release Highlights

This release further improves our TypeScript support with consistent enum naming and a better list of exported types.

Bug Fixes

Documentation

We invite you to try the mongodb package immediately, and report any issues to the NODE project.

Loading

v3.6.9

26 May 21:18
@dariakp dariakp
v3.6.9
394832a
This commit was signed with the committer’s verified signature.
dariakp Daria Pardue
GPG key ID: A686E99780FAD44A
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.6.9

The MongoDB Node.js team is pleased to announce version 3.6.9 of the driver!

Release Highlights

This release fixes a major performance bug in bulk write operations, which was inadvertently introduced by an incomplete code change in the previous release. The bug resulted in redundant array iterations and caused exponential increases in bulk operation completion times. Thank you Jan Schwalbe for bringing this to our attention!

Bug Fixes

Documentation

We invite you to try the mongodb package immediately, and report any issues to the NODE project.

Loading

v3.6.8

21 May 17:25
@nbbeeken nbbeeken
v3.6.8
6c8cc84
This commit was signed with the committer’s verified signature.
nbbeeken Neal Beeken
GPG key ID: 22F3C38EA1A0C076
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.6.8

The MongoDB Node.js team is pleased to announce version 3.6.8 of the mongodb package!

Release Highlights

Thanks to the quick adoption of the previous new patch by the mongoose package (Automattic/mongoose#10265) a small bug was identified when connections to mongodb would timeout causing unnecessary clean up operations to run. Thank you @vkarpov15!

Bug Fixes

Documentation

We invite you to try the mongodb package immediately, and report any issues to the NODE project.

Loading

v4.0.0-beta.4

18 May 18:41
@nbbeeken nbbeeken
v4.0.0-beta.4
3a2ea28
This commit was signed with the committer’s verified signature.
nbbeeken Neal Beeken
GPG key ID: 22F3C38EA1A0C076
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.0.0-beta.4 Pre-release
Pre-release

The MongoDB Node.js team is pleased to announce version 4.0.0.beta.4 of the driver.

Release Highlights

This beta release brings optional support for Typescript generics when defining your collections

// Example:
interface Pet {
    type: 'cat' | 'dog' | 'fish'
}
const collection = db.collection<Pet>()
await collection.findOne({}).toArray() // returns Pet[]

as well as strong typing for events emitted by the MongoClient. For example, when listening to .on('commandStarted' event => ...), event here will be a CommandStartedEvent object.

We have a few breaking changes listed below, notably the node driver now aligns with other drivers by using the returnDocument option when determining whether to return the document before or after the update in findOneAndUpdate and findOneAndReplace.

⚠ BREAKING CHANGES

Features

Bug Fixes

Documentation

We invite you to try the driver immediately, and report any issues to the NODE project.

To try the beta use the following command:

npm install [email protected]

Thanks very much to all the community members who contributed to this release!

Loading

v3.6.7

18 May 19:25
@nbbeeken nbbeeken
v3.6.7
4fd03e8
This commit was signed with the committer’s verified signature.
nbbeeken Neal Beeken
GPG key ID: 22F3C38EA1A0C076
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.6.7

The MongoDB Node.js team is pleased to announce version 3.6.7 of the driver

Release Highlights

This patch addresses a number of bug fixes. Notably, there was an interesting javascript related issue with sorting documents. It only impacts users using numerical keys in their documents.

> { a: 'asc', [23]: 'asc' }
{ [23]: 'asc', a: 'asc' } // numbers come first

In javascript, numerical keys are always iterated first when looping over the keys of an object followed by the chronological specification of each string key. This effectively changes the ordering of a sort document sent to mongodb. However our driver does accept sort specification in a variety of ways and one way to avoid this problem is passing an array of tuples:

[['a', 'asc'], ['23', 'asc']]

This ensures that mongodb is sent the 'a' key as the first sort key and '23' as the second.

Bug Fixes

Documentation

We invite you to try the driver immediately, and report any issues to the NODE project.

Thanks very much to all the community members who contributed to this release!

Loading

v4.0.0-beta.3

06 Apr 19:28
@nbbeeken nbbeeken
v4.0.0-beta.3
d477e2e
This commit was signed with the committer’s verified signature.
nbbeeken Neal Beeken
GPG key ID: 22F3C38EA1A0C076
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.0.0-beta.3

The MongoDB Node.js team is pleased to announce version 4.0.0-beta.3 of the driver

This release brings us closer to the RC release for the fully typescript enabled version 4.0.0 of the driver.
You can expect a full migration and detailed list of changes with the upcoming RC.

All Changes

Documentation

Loading

v3.6.6

06 Apr 19:56
@nbbeeken nbbeeken
v3.6.6
dfb03ad
This commit was signed with the committer’s verified signature.
nbbeeken Neal Beeken
GPG key ID: 22F3C38EA1A0C076
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.6.6

The MongoDB Node.js team is pleased to announce version 3.6.6 of the driver

Release Highlights

This patch addresses a number of bugs listed below.
Most notably, for client side encryption users upgrading to this version of the driver along with the new version of [email protected] will alleviate the potential deadlock case if your connection pool was fully utilized. There will now be an internal MongoClient that will be used for metadata look ups (e.g, listCollections) when the pool size is under certain constraints. The events generated from this client are forwarded to the client instance you initialize so it is possible to monitor all events.

Bug

  • [NODE-2995] - Sharing a MongoClient for metadata lookup can lead to deadlock in drivers using automatic encryption
  • [NODE-3050] - Infinite loop on Windows due to a bug in require_optional package
  • [NODE-3120] - TypeError: Cannot read property 'roundTripTime' of undefined
  • [NODE-3122] - Pipelining an upload stream of GridFSBucket never finishes on Node v14
  • [NODE-3129] - Collection () .. .setReadPreference() not routing query to secondaries
  • [NODE-3133] - autoEncryption produces serverHeartbeatFailed - with MongoError typemismatch

Improvement

  • [NODE-3070] - Define error handling behavior of writeErrors and writeConcernError on Mongos

Documentation

We invite you to try the driver immediately, and report any issues to the NODE project.

Thanks very much to all the community members who contributed to this release!

Loading

v4.0.0-beta.2

16 Mar 14:58
@nbbeeken nbbeeken
v4.0.0-beta.2
f1eabf4
This commit was signed with the committer’s verified signature.
nbbeeken Neal Beeken
GPG key ID: 22F3C38EA1A0C076
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.0.0-beta.2 Pre-release
Pre-release

The MongoDB Node.js team is pleased to announce version 4.0.0-beta.2 of the driver

This release brings us closer to the RC release for the fully typescript enabled version 4.0.0 of the driver.
You can expect a full migration and detailed list of changes with the upcoming RC.

Breaking Changes

All Changes

  • add FLE AWS sessionToken TypeScript definitions (#2737) (f4698b5)
  • remove catch for synchronous socket errors and remove validation on nodejs option (#2746) (a516903)
  • session support detection spec compliance (#2733) (1615be0)
  • remove deprecated items (#2740) (ee1a4d3)
  • remove enums in favor of const objects (#2741) (d52c00e)

Documentation

Reference: https://docs.mongodb.com/drivers/node
API: https://mongodb.github.io/node-mongodb-native/4.0
Changelog: https://github.com/mongodb/node-mongodb-native/blob/4.0/HISTORY.md

Loading

v3.6.5

16 Mar 15:17
@nbbeeken nbbeeken
v3.6.5
6887e8d
This commit was signed with the committer’s verified signature.
nbbeeken Neal Beeken
GPG key ID: 22F3C38EA1A0C076
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.6.5

The MongoDB Node.js team is pleased to announce version 3.6.5 of the driver!

Notable Fixes

In this patch there is a fix surrounding an issue some users were encountering in serverless environments when using the Unified Topology. If the nodejs process went unused for a great amount of time there was an intermittent issue that would cause startSession to fail, however, issuing a dummy read request would resolve the problem. The session support check is now done after server selection meaning the driver has the most up to date information about the MongoDB deployment before utilizing sessions. We encourage any user's that implemented workarounds to updated their driver and make use of this fix.

In addition, the previous release of our driver added a warning about an upcoming change in the v4 version of the driver about how users can specify their write concern options. We've updated the driver to use nodejs's process.emitWarning API in nearly all cases where the driver prints something out, as well as limit most warning messages to only be printed once.

Bug

  • session support detection spec compliance (#2732) (9baec71)
  • [NODE-3100] - startSession fails intermittently on servers that support sessions
  • [NODE-3066] - Accessing non-existent property 'MongoError' of module exports inside circular dependency
  • [NODE-3114] - Incorrect warning: Top-level use of w, wtimeout, j, and fsync is deprecated
  • [NODE-3119] - Node 14.5.4, mongo 3.6.4 Circular warnings
Loading