fix(mediasoup-sdp-bridge): support mediasoup-client 3.10.x (#685)

mediasoup-client 3.8.0 added an "exports" field that hides the
internal `lib/` subpaths the bridge was importing, breaking the
package with ERR_PACKAGE_PATH_NOT_EXPORTED on any 3.8+ install.
Move the imports to the public paths exposed since 3.10.0
(mediasoup-client/handlers/sdp/*, mediasoup-client/ortc) and read
IceCandidate from the publicly re-exported mediasoup-client/types.
Drop the now-removed extmapAllowMixed option on RemoteSdp.send,
and tighten the peerDependency to >=3.10.0 <3.11.0 to signal the
tested range. 3.11 added a mandatory third arg to
getExtendedRtpCapabilities and 3.16 renamed validateRtpCapabilities;
both need follow-up before they can be supported.

Author: mcottontensor

.changeset/mediasoup-sdp-bridge-3.10.md

@@ -0,0 +1,5 @@
+---
+"@epicgames-ps/mediasoup-sdp-bridge": patch
+---
+
+Make `mediasoup-sdp-bridge` importable against `mediasoup-client` 3.10.x (#685). Internal subpaths under `mediasoup-client/lib/...` were hidden by the `exports` field added in 3.8.0, breaking `import * as MsSdpUtils from "mediasoup-client/lib/handlers/sdp/commonUtils"` etc. with `ERR_PACKAGE_PATH_NOT_EXPORTED`. The imports now use the public paths exposed since 3.10.0 (`mediasoup-client/handlers/sdp/commonUtils`, `mediasoup-client/handlers/sdp/RemoteSdp`, `mediasoup-client/handlers/sdp/unifiedPlanUtils`, `mediasoup-client/ortc`) and the publicly re-exported `IceCandidate` from `mediasoup-client/types`. The peerDependency is tightened to `>=3.10.0 <3.11.0` to flag the supported range — 3.11 added a mandatory third arg to `getExtendedRtpCapabilities` and 3.16 renamed `validateRtpCapabilities`, both of which need follow-up work before they can be supported. The unsupported `extmapAllowMixed` option on `RemoteSdp.send` was removed.

Extras/mediasoup-sdp-bridge/package.json

@@ -64,14 +64,14 @@
     "jest": "^29.7.0",
     "jest-tobetype": "^1.2.3",
     "mediasoup": "3.15.5",
-    "mediasoup-client": "3.9.1",
+    "mediasoup-client": "~3.10.0",
     "open-cli": "^6.0.1",
     "prettier": "~2.5.0",
     "tsc-watch": "^4.2.8",
     "typescript": "^5.7.3"
   },
   "peerDependencies": {
     "mediasoup": "^3.0.0",
-    "mediasoup-client": "^3.0.0"
+    "mediasoup-client": ">=3.10.0 <3.11.0"
   }
 }

Extras/mediasoup-sdp-bridge/src/SdpUtils.ts

@@ -1,10 +1,10 @@
 // TODO, FIXME: Here we're assuming that Unified Plan is the correct way to
 // handle the SDP messages. For a more robust handling, this should probably
 // depend on the actual type of SDP: plain, PlanB, or UnifiedPlan.
-import * as MsSdpUnifiedPlanUtils from "mediasoup-client/lib/handlers/sdp/unifiedPlanUtils";
+import * as MsSdpUnifiedPlanUtils from "mediasoup-client/handlers/sdp/unifiedPlanUtils";
 
-import * as MsSdpUtils from "mediasoup-client/lib/handlers/sdp/commonUtils";
-import * as MsOrtc from "mediasoup-client/lib/ortc";
+import * as MsSdpUtils from "mediasoup-client/handlers/sdp/commonUtils";
+import * as MsOrtc from "mediasoup-client/ortc";
 import {
   MediaKind,
   RtpCapabilities,

Extras/mediasoup-sdp-bridge/src/index.ts

@@ -1,6 +1,6 @@
-import * as MsSdpUtils from "mediasoup-client/lib/handlers/sdp/commonUtils";
-import { RemoteSdp } from "mediasoup-client/lib/handlers/sdp/RemoteSdp";
-import { IceCandidate as ClientIceCandidate } from "mediasoup-client/lib/Transport";
+import * as MsSdpUtils from "mediasoup-client/handlers/sdp/commonUtils";
+import { RemoteSdp } from "mediasoup-client/handlers/sdp/RemoteSdp";
+import { IceCandidate as ClientIceCandidate } from "mediasoup-client/types";
 
 import {
   Consumer,
@@ -208,7 +208,6 @@ export class SdpEndpoint {
         offerRtpParameters: this.producerOfferParams[i],
         answerRtpParameters: this.producers[i].rtpParameters,
         codecOptions: undefined,
-        extmapAllowMixed: false,
       });
     }