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

Update project dependencies

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • 3
    • Not Needed
    • None
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      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
        • bson/etc/eslint/no-bigint-usage
        • legacy driver
        • mongo-client-encryption
        • kerberos
        • zstd
        • dbx-js-tools
        • mongodb-connection-string-url
      • Update github actions (use the open dependabot PRs)
      • 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
          • Do NOT update prettier, eslint, or any other code formatter major versions if it would result in a reformatting of the entire code base
        • 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
        • 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
        • Note that the aws sdk must stay at the version supported in lambda (AWS documents)
        • 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
      • Update the prod dependencies to the latest safe and semver-compatible versions
        • Do not upgrade peer dependencies, because that is breaking - someone's build that was passing before can start failing because they didn't manually install an upgraded version of the peer dep
        • 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

            Assignee:
            durran.jordan@mongodb.com Durran Jordan
            Reporter:
            dbeng-pm-bot TPM Jira Automations Bot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None