Use Case

As a driver developer,
I want our packages to compile with TS 6.x,
So that we can stay up-to-date with Typescript releases.

As a driver user,
I want the driver's public types to be compatible with TS 6.x,
So that I can use TS 6.x in my projects.

TS 6.0 work seems to have begun ({{ npm i typescript@next }} now installs 6.0 releases). It is too early to say exactly what impact this major release will have on the Node team's codebases, but we should be prepared to adopt the changes once they're available.

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
• Is there an opportunity for better cross-driver alignment or testing in this area?
• Is there an opportunity to improve existing documentation on this subject?

Acceptance Criteria

Implementation Requirements

• functional reqs, potential snafus to avoid, performance targets, etc

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• DOCSP ticket, API docs, etc

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