Upgrade Driver Versions
On this page
Overview
On this page, you can learn how to upgrade your driver to a new version. This page also includes the changes you must make to your application to upgrade your driver without losing functionality, if applicable.
How to Upgrade
Before you upgrade, perform the following actions:
Ensure the new driver version is compatible with the MongoDB Server version your application connects to and the version of Node.js that your application runs on. See the Compatibility page for this information.
Address any breaking changes between the version of the driver your application uses now and your planned upgrade version in the Breaking Changes section of this guide. To learn more about the MongoDB Server release compatibility changes, see the Server Release Compatibility Changes section.
Tip
You can minimize the amount of changes that you must make to your application when upgrading driver versions by using the Stable API.
To upgrade your driver version, run the following command in your application's directory:
npm install mongodb@6.11
To upgrade to a different version of the driver, replace the information after the
@
symbol with your preferred version number. For more information about the
npm install
command, see the npm-install
npm documentation.
Breaking Changes
A breaking change is a modification in a convention or behavior in a specific version of the driver that may prevent your application from working as expected.
The breaking changes in this section are categorized by the major version releases that introduced them. When upgrading driver versions, address all the breaking changes between your current version and the planned upgrade version. For example, if you are upgrading the driver from v3.x to v5.x, address all breaking changes listed under v4.0 and v5.0.
Version 6.0 Breaking Changes
Version 6.0 of the Node.js driver requires Node.js v16.20.1 or later.
The driver removes support for the
addUser()
helper command. Use the createUser MongoDB Shell command instead.The driver removes support for the
collStats
operation. Use the $collStats aggregation operator instead.The driver removes all the deprecated
ssl
-prefixed options and thetlsCertificateFile
option in theMongoClientOptions
type. Create aSecureContext
object or set thetls
-prefixed options in yourMongoClientOptions
instance instead.The driver reads files set in the
tlsCAFile
andtlsCertificateKeyFile
connection options when you call theMongoClient.connect()
method, not when you create theMongoClient
instance.The driver removes the
keepAlive
andkeepAliveInitialDelay
connection options. The value ofkeepAlive
is permanently set totrue
and the value ofkeepAliveInitialDelay
is set to 300000 milliseconds (300 seconds).The
Db.command()
method accepts only options that are not related to a specific command. To learn more about these options, see the Command Options section of the Run a Command guide.If you add
mongodb-client-encryption
as a dependency, the major version number must match that of the Node.js driver. For example, Node.js driver v6.x.x requiresmongodb-client-encryption
v6.x.x.Automatic Encryption methods are now in the Node.js driver. You must import these methods from the driver instead of from
mongodb-client-encryption
.Removed the
ObjectId
constructor that accepted a 12-character string.Modified
abortTransaction()
andcommitTransaction()
methods to returnnull
instead of the raw command results.Removed connection option helpers that accepted values other than
true
orfalse
as booleans. You must provide eithertrue
orfalse
values in the connection string or to the MongoClient constructor.Removed the
Binary
BSON type constructor that accepted a string.The
Binary.write()
method no longer accepts a string to write to the binary BSON object.The ClientEncryption API returns promises instead of callbacks.
The
socks
package, which enables SOCKS5 proxy support, is a peer-optional dependency. You must install the package to enable SOCKS5 in your application. To learn more, see Enable SOCKS5 Proxy Support.If you start a session on a client, then pass that session to a different client, the driver throws an error when you perform any operations in the session.
The
includeResultMetadata
option for compound operation methods isfalse
by default. See the Built-in Methods section of the Compound Operations guide for more information.The
withSession()
method returns the value that the provided function returns. In previous driver versions, this method returnsundefined
. ThewithTransaction()
method returns the value that the callback returns. In previous driver versions, this method returns the server command response, which varies depending on the MongoDB Server version or type that the driver connects to. To learn more about transactions, see the Perform a Transaction usage examples and the Transactions guide.Raised the optional
kerberos
dependency minimum version to 2.0.1 and removed support for version 1.x.Raised the optional
zstd
dependency minimum version to 1.1.0.
Version 5.0 Breaking Changes
The driver is no longer compatible with Node.js v12 or earlier. If you want to use this version of the driver, you must use Node.js v14.20.1 or greater.
The driver removes support for callbacks in favor of a promise-based API. The following list provides some strategies for callback users to adopt this version:
Migrate to the promise-based API (recommended)
Use the promise-based API and
util.callbackify
Add
mongodb-legacy
to continue using callbacks
For more information about these strategies, see the v5.0 changelog.
The driver removes support for the
Collection.insert()
,Collection.update()
, andCollection.remove()
helper methods. The following list provides instructions on how to replace the functionality of the removed methods:Migrate from
Collection.insert()
toinsertOne()
orinsertMany()
Migrate from
Collection.update()
toupdateOne()
orupdateMany()
Migrate from
Collection.remove()
todeleteOne()
ordeleteMany()
The driver no longer includes AWS SDK modules by default.
The driver no longer automatically imports the
bson-ext
package.The driver removes support for custom
Promise
libraries. The driver no longer supports thepromiseLibrary
option ofMongoClient
and thePromise.set
export that allows specifying a customPromise
library.The driver removes support for the
Collection.mapReduce()
helper.The
BulkWriteResult
type no longer has the publicly enumerableresult
property.The following types, options, and methods have been removed:
BulkResult.lastOp()
methodopTime
property ofBulkResult
BulkWriteOptions.keepGoing
optionWriteConcernError.err()
methodAddUserOptions.digestPassword
optionKerberos
gssapiCanonicalizeHostName
optionslaveOk
options and method removed in favor ofsecondaryOk
ObjectID
type removed in favor ofObjectId
AsyncIterator
interface removed in favor ofAsyncGenerator
Version 4.0 Breaking Changes
The driver is no longer compatible with Node.js v12.8 or earlier. If you want to use this version of the driver, you must use Node.js v12.9 or greater.
Cursor
types no longer extendReadable
directly.You cannot use a
ChangeStream
instance as an iterator after using it as anEventEmitter
. You also cannot do the reverse—using anEventEmitter
instance as an iterator after using it as aChangeStream
.The following methods no longer accept a callback parameter:
Collection.find()
Collection.aggregate()
Db.aggregate()
The default value of the
maxPoolSize
connection option is now100
.The driver no longer supports the
gssapiServiceName
Kerberos option. UseauthMechanismProperties.SERVICE_NAME
instead.The driver no longer accepts non-boolean types, such as
0
or1
, for boolean options.The
db.collection
type no longer accepts a callback.The
Db
type is no longer anEventEmitter
. You can listen to any events directly from theMongoClient
instance.The driver removes support for the
Collection.group()
helper.The driver no longer includes the deprecated
GridStore
API.
For more information about these changes, see the v4.0 changelog.
Server Release Compatibility Changes
A server release compatibility change is a modification to the driver that discontinues support for a set of MongoDB Server versions.
The driver discontinues support for a MongoDB Server version after it reaches end-of-life (EOL).
To learn more about the MongoDB support for EOL products, see the Legacy Support Policy.
Version 4.2 Server Release Support Changes
The v4.2 driver drops support for MongoDB Server v3.4 and earlier. To use the v4.2 driver, your MongoDB Server must be v3.6 or later. To learn how to upgrade your MongoDB Server deployment, see Release Notes in the MongoDB Server manual.