Use Case

node-gyp 11+ only supports Node18+; we should upgrade to the latest node-gyp we can once we drop support for Node16.

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

• We could run into problems if node-gyp 11+ has breaking changes relative to prebuild, because we have the following override:

"overrides": {
    "prebuild": {
      "node-gyp": "$node-gyp" // v10.1.0, because that's what our dependency is set to, to get it to work on python3 (older versions of node-gyp call into python2)
    }
  },

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