-
Type:
Build Failure
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: TypeScript
-
0
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Use Case
As a... Node developer
I want... upgrade @types/node dependency from 22 to 24
So that... I can use the latest Node.js type definitions and features in my project
User Experience
- What is the desired/expected outcome for the user once this ticket is implemented?
- Driver is on version 24 of @types/node
Dependencies
- upstream and/or downstream requirements and timelines to bear in mind
- None
Risks/Unknowns
- What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
- When we tried to upgrade from 22 to 24 (as part of https://jira.mongodb.org/browse/NODE-7237), we saw build breaks.
- In (cursor.test-d.ts line 38)https://github.com/mongodb/node-mongodb-native/blob/main/test/types/community/cursor.test-d.ts#L38, the variable "doc" changes its type from a specific type to "any".
- This may be caused by v24 changes to "Readable".
- If transition to v24 without fixing this issue (ie by skipping/removing this test), customers will be broken because of the type change.
- Is there an opportunity for better cross-driver alignment or testing in this area?
- No
- Is there an opportunity to improve existing documentation on this subject?
- No
Acceptance Criteria
Implementation Requirements
- functional reqs, potential snafus to avoid, performance targets, etc
- @types/node is on version 24.* and builds/tests are succeeding
- In (cursor.test-d.ts line 38)https://github.com/mongodb/node-mongodb-native/blob/main/test/types/community/cursor.test-d.ts#L38, the variable "doc" is NOT of type "any".
Testing Requirements
- unit test, spec test sync, etc
- all tests are passing
Documentation Requirements
- DOCSP ticket, API docs, etc
- None
Follow Up Requirements
- additional tickets to file, required releases, etc
- if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward
- None
- backported by
-
NODE-7237 Update dependencies for driver main
-
- Closed
-