Releases: mongodb/js-bson
v7.0.0-alpha.1
v7.0.0-alpha
7.0.0-alpha (2025-10-21)
⚠ BREAKING CHANGES
- NODE-7098: use bigint literal syntax (#826)
- NODE-5763: remove support for new ObjectId() (#824)
- NODE-6625: remove support for Node 16 and 18 (#821)
Features
- NODE-5763: remove support for new ObjectId(<number>) (#824) (21cc3ff)
- NODE-6321: remove require('crypto') from Nodejs bundle (#825) (7ba8917)
- NODE-6625: remove support for Node 16 and 18 (#821) (f636254)
- NODE-7019: remove react native vendor polyfills (#827) (883f238)
- NODE-7098: use bigint literal syntax (#826) (94bf732)
- NODE-7099: deprecate BSON binary subtype 2 constant (#812) (f61946d)
- NODE-7255: add well-known Symbol alias for
_bsontype(#829) (1e1b619)
v6.10.4
6.10.4 (2025-06-02)
The MongoDB Node.js team is pleased to announce version 6.10.4 of the bson package!
Release Notes
Top-Level Await removed from the browser BSON bundle
In versions <6.10.4, BSON uses a top-level await to asynchronously import the crypto module. This change unintentionally caused headaches for users of webpack, react native, vite and other tools bundlers and tools.
The top-level await has been removed from all BSON bundles. Thanks to @lourd for this contribution.
Prevent the creation of incorrectly sized float32 vectors
This adds validation to our BSON.serialize and EJSON.stringify methods that will prevent creating float 32 vectors that are not a multiple of 4. Previously created vectors that do not meet this validation will still be deserialized and parsed so they can be fixed.
Additionally, the toFloat32Array(), toInt8Array(), and toPackedBits() methods now perform the same validation that serialize does to prevent use of incorrectly formatted Binary vector values. (For example, a packed bits vector with more than 7 bits of padding)
Vectors of an incorrect length could only be made manually (directly constructing the bytes and calling new Binary). We recommend using toFloat32Array and fromFloat32Array when interacting with Vectors in MongoDB as they handle the proper creation and translation of this data type.
Bug Fixes
- NODE-6074: Removes top-level await in bson with separate node and browser ESM bundles (#749) (4602973)
- NODE-6735, NODE-6711: add BSON vector validation to EJSON stringification, serialization and conversion to native types (#748) (64ff6a2)
Documentation
We invite you to try the bson library immediately, and report any issues to the NODE project.
Contributors
Assets 4
v6.9.1
6.9.1 (2025-03-06)
The MongoDB Node.js team is pleased to announce version 6.9.1 of the bson package!
Release Notes
⚠️ Fixed potential data corruption bug when useBigInt64 is enabled
After refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing Long values with the useBigInt64 flag enabled. The bug would lead to negative Long values being deserialized as unsigned integers. This issue has been resolved here.
Thanks to @rkistner for reporting this bug!
Bug Fixes
Documentation
We invite you to try the bson library immediately, and report any issues to the NODE project.
Contributors
Assets 4
v6.8.1
6.8.1 (2025-03-06)
The MongoDB Node.js team is pleased to announce version 6.8.1 of the bson package!
Release Notes
⚠️ Fixed potential data corruption bug when useBigInt64 is enabled
After refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing Long values with the useBigInt64 flag enabled. The bug would lead to negative Long values being deserialized as unsigned integers. This issue has been resolved here.
Bug Fixes
Documentation
We invite you to try the bson library immediately, and report any issues to the NODE project.
v6.7.1
6.7.1 (2025-03-06)
The MongoDB Node.js team is pleased to announce version 6.7.1 of the bson package!
Release Notes
⚠️ Fixed potential data corruption bug when useBigInt64 is enabled
After refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing Long values with the useBigInt64 flag enabled. The bug would lead to negative Long values being deserialized as unsigned integers. This issue has been resolved here.
Bug Fixes
Documentation
We invite you to try the bson library immediately, and report any issues to the NODE project.
v6.6.1
6.6.1 (2025-03-06)
The MongoDB Node.js team is pleased to announce version 6.6.1 of the bson package!
Release Notes
⚠️ Fixed potential data corruption bug when useBigInt64 is enabled
After refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing Long values with the useBigInt64 flag enabled. The bug would lead to negative Long values being deserialized as unsigned integers. This issue has been resolved here.
Bug Fixes
Documentation
We invite you to try the bson library immediately, and report any issues to the NODE project.
v6.5.1
6.5.1 (2025-03-06)
The MongoDB Node.js team is pleased to announce version 6.5.1 of the bson package!
Release Notes
⚠️ Fixed potential data corruption bug when useBigInt64 is enabled
After refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing Long values with the useBigInt64 flag enabled. The bug would lead to negative Long values being deserialized as unsigned integers. This issue has been resolved here.
Thanks to @rkistner for reporting this bug!
Bug Fixes
Documentation
We invite you to try the bson library immediately, and report any issues to the NODE project.
Contributors
Assets 4
v6.4.1
6.4.1 (2025-03-05)
The MongoDB Node.js team is pleased to announce version 6.4.1 of the bson package!
Release Notes
⚠️ Fixed potential data corruption bug when useBigInt64 is enabled
After refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing Long values with the useBigInt64 flag enabled. The bug would lead to negative Long values being deserialized as unsigned integers. This issue has been resolved here.
Fixed float byte-wise handling on big-endian systems
Caution
Among the platforms BSON and the MongoDB driver support this issue impacts s390x big-endian systems. x86, ARM, and other little-endian systems are not affected. Existing versions of the driver can be upgraded to this release.
A change in [email protected] (2024-02-29) started parsing and serializing floats using a Float64Array. When reading the bytes from this array the ordering is dependent on the platform it is running on and we now properly account for that ordering.
Bug Fixes
- NODE-6812: incorrect negative bigint handling (#762) (ce3e544)
- NODE-6818: flip byte order depending on system endianness (#766) (8a55718)
Documentation
We invite you to try the bson library immediately, and report any issues to the NODE project.
v6.10.3
6.10.3 (2025-02-19)
The MongoDB Node.js team is pleased to announce version 6.10.3 of the bson package!
Release Notes
⚠️ Fixed potential data corruption bug when useBigInt64 is enabled
After refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing Long values with the useBigInt64 flag enabled. The bug would lead to negative Long values being deserialized as unsigned integers. This issue has been resolved here.
Thanks to @rkistner for reporting this bug!
Bug Fixes
Documentation
We invite you to try the bson library immediately, and report any issues to the NODE project.