Dependency version between @sap-cloud-sdk packages

[carlonnheim]

Hi,

We are experiencing issues with the versioning of dependencies between @Sisn-cloud-sdk packages. If we bring in one of the packages alone, that will in turn bring other packages as dependencies. The semver of these dependencies will pick higher versions of the other packages.

For example https://github.com/SAP/cloud-sdk-js/blob/v3.15.0/packages/odata-v2/package.json

  "dependencies": {
    "@sap-cloud-sdk/connectivity": "^3.15.0",
    "@sap-cloud-sdk/http-client": "^3.15.0",
    "@sap-cloud-sdk/odata-common": "^3.15.0",
    "@sap-cloud-sdk/util": "^3.15.0",
    "bignumber.js": "^9.1.2",
    "moment": "^2.30.1",
    "uuid": "^9.0.1"
  },

If we add a single package to a project which is not the latest version this causes a mix of @Sisn-cloud-sdk versions depending on which packages we explicitly bring in. In particular when adding parts of the cloud-sdk over time.

Is there any advise on how to handle these dependencies? Should not the expected result of bringing in one of the cloud-sdk packages be that dependent packages are also loaded at the same version (i.e. the semver of the cross-dependencies should be more restrictive?).

Thanks in advance for any clarification on this subject

//Carl