investigate @types/node upgrade issues from 22 to 24

XMLWordPrintableJSON

    • 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)
      • 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

      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

            Assignee:
            Pavel Safronov
            Reporter:
            Pavel Safronov
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: