Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6585

Update minimum supported Node version

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Use Case

      As a driver engineer,

      I want to stay up to date with our supported Node versions,

      So that we do not need to support long EOL'd node versions and so that we can use newer js syntax and features.

      User Experience

      • Users will see deprecation warnings when using our packages with unsupported node versions

      Dependencies

      • Requires mongosh/compass to have dropped support for Node16.

      Risks/Unknowns

      • Unsure.

      Acceptance Criteria

      Implementation Requirements

      • Adjust the minimum supported version to the lowest LTS (at time of Node v7)
      • (native bindings only)
        • Remove support for Node16 in ci
          • No need to test on ubuntu bionic for Node16 anymore
        • Upgrade node-gyp to the latest version (the current node-gyp version is pinned because it doesn't work with <python 3.8, and python3.8 is not available to download using apt-get on ubuntu)

      Testing Requirements

      • n/a

      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

            Assignee:
            Unassigned Unassigned
            Reporter:
            bailey.pearson@mongodb.com Bailey Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: