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

Update project dependencies

    • 5
    • Not Needed
    • Not Needed
    • 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... Node driver engineer
      I want... to have up to date dependencies
      So that... we can be more efficient by using the best available tools

      User Impact

      • N/A

      Dependencies

      • N/A

      Unknowns

      • Do we want to update any previous majors?

      Acceptance Criteria

      Implementation Requirements

      • Review and update the dev and prod dependencies in the following libraries:
        • driver
        • js-bson
        • legacy driver
        • mongo-client-encryption
        • kerberos
        • zstd
      • Update the dev dependencies to latest available compatible versions
        • Update the major version if and ONLY if this can be done with minimal code changes
        • Don't update the version of mongodb in mongodb-legacy's prod dependencies outside of a major version bump, since we want users to be able to use it across all minor versions of a given driver major
        • Do NOT update prettier, eslint, or any other code formatter major versions if it would result in a reformatting of the entire code base
        • ANY reformatting MUST be done in a separate pull request and should ONLY be done if the team agrees that it is an important improvement
        • If there is compelling reason to adopt a major dependency version that would require significant code changes or reformatting, file a separate ticket to triage with the team
      • Update the prod dependencies to the latest safe and semver-compatible versions
        • If the current major version is no longer supported, file a separate ticket to address this
      • Updating TS is NOT part of this ticket, file a separate ticket if an update is available and desirable

      Testing Requirements

      • All existing tests should continue to pass

      Documentation Requirements

      • N/A

        There are no Sub-Tasks for this issue.

            Assignee:
            bailey.pearson@mongodb.com Bailey Pearson
            Reporter:
            dbeng-pm-bot PM Bot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: