-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: 7.1.1
-
Component/s: TypeScript
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Use Case
As a developer using TypeScript 6+
I want moduleResolution updated from "node10" to "node16" or "NodeNext"
So that the package doesn't trigger deprecation warnings and won't break in TypeScript 7.0
User Experience
- node_modules/mongodb/tsconfig.json has "moduleResolution": "node10"
- TypeScript 6 warns: "Option 'moduleResolution=node10' is deprecated and will stop functioning in TypeScript 7.0"
- Non-blocking today (skipLibCheck bypasses it), will break in TS 7.0
Risks/Unknowns
- Will fail when TypeScript 7.0 removes node10 support
Acceptance Criteria
- Change moduleResolution to "node16" or "NodeNext" in tsconfig.json
Testing Requirements
- Verify package builds and .d.ts output is unchanged