[Bot] Update UE5.5 NPM Changelogs

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to UE5.5, this PR will be updated.

Releases

@epicgames-ps/lib-pixelstreamingfrontend-ue5.5@1.3.0

Minor Changes

• 113a3c1: Add an AutoEnterVR config flag ([Feature Request] Automatically enter VR Mode ? #461). When enabled, the player checks for immersive-vr support after the video is initialized and requests the WebXR session automatically. Default is off. Note: browsers may require a user gesture to start a WebXR session; in flows where there is no pending gesture (for example, a fresh-page-load AutoConnect) the request can still be rejected and the player will log a warning.
• c3779a5: Added Viewport Resolution Scale parameter to request higher resolution streams on small screens

Patch Changes

• 0d87533: Synthesize a MouseUp after MouseDouble in both mouse controllers so the streamer's pressed-button state stays balanced after a double-click ([Bug] When a user double-clicks, UE doesn't receive the second release #10). The plugin treats MouseDouble as a press-class event (RoutePointerDoubleClickEvent / IGenericApplicationMessageHandler::OnMouseDoubleClick) but never synthesizes a release; the browser's preceding mouseup was already consumed by the prior MouseUp, so UE was left thinking the button was still held — manifesting, for example, as camera pans that latched on after a double-click. Behaviour is gated on the new MouseDoubleClickAutoRelease flag (default on); disable it via ?MouseDoubleClickAutoRelease=false or the settings panel to restore pre-fix behaviour for projects that handle the doubleclick release themselves.
• b16fd54: - Addressing security issues raised by dependabot. (glob, js-yaml, playwright)
  • Added lint npm script to the root project. Running npm run lint will now run linting over all packages.
• af7bde1: Map the macOS Command (and Windows Meta) keys to UE keycodes 91 (LeftWindowKey) and 92 (RightWindowKey). KeyCodes.ts now contains MetaLeft/MetaRight (and the legacy OSLeft/OSRight) entries, and KeyboardController.getKeycode normalizes the right-Cmd code so it no longer collides with ContextMenu (93) on browsers that report keyCode === 93 for it, and so Firefox-on-Mac (which reports keyCode === 224 for both Cmds) is also handled. Frontend portion of issue [Bug] Missing macOS Command Key Detection in Pixel Streaming's KeyboardController #276 — UE-side support for these key codes is tracked separately.
• a7d9e91: Fix mouse-button-held tracking so dragging outside the video element keeps sending move and release events to UE ([Feature Request] - capture mouse while mouse down and outside video element #349). When a button is pressed on the hovering mouse controller, mousemove/mouseup are temporarily moved from the video element to window, with coordinates re-computed against the video element's bounding rect. When all buttons are released, the listeners switch back to the element. This prevents the engine from being left with a stuck button when the user releases outside the video — common with DefaultViewportMouseCaptureMode=CaptureDuringMouseDown.
• e948750: Make npm run lint work regardless of the directory it's invoked from. Each workspace's eslint.config.mjs now pins parserOptions.tsconfigRootDir to import.meta.dirname, so parserOptions.project resolves relative to the config file's own directory rather than whichever CWD typescript-eslint happens to pick by default. Previously the six workspace configs prefixed project with the workspace directory (e.g. 'Common/tsconfig.cjs.json'), which only worked under one specific typescript-eslint version's resolution behavior and broke CI when run from within the workspace.
• Updated dependencies [b16fd54]
• Updated dependencies [e948750]
  • @epicgames-ps/lib-pixelstreamingcommon-ue5.5@0.3.3

@epicgames-ps/lib-pixelstreamingfrontend-ui-ue5.5@1.4.0

Minor Changes

• c3779a5: Added Viewport Resolution Scale parameter to request higher resolution streams on small screens

Patch Changes

• 0d87533: Synthesize a MouseUp after MouseDouble in both mouse controllers so the streamer's pressed-button state stays balanced after a double-click ([Bug] When a user double-clicks, UE doesn't receive the second release #10). The plugin treats MouseDouble as a press-class event (RoutePointerDoubleClickEvent / IGenericApplicationMessageHandler::OnMouseDoubleClick) but never synthesizes a release; the browser's preceding mouseup was already consumed by the prior MouseUp, so UE was left thinking the button was still held — manifesting, for example, as camera pans that latched on after a double-click. Behaviour is gated on the new MouseDoubleClickAutoRelease flag (default on); disable it via ?MouseDoubleClickAutoRelease=false or the settings panel to restore pre-fix behaviour for projects that handle the doubleclick release themselves.
• b16fd54: - Addressing security issues raised by dependabot. (glob, js-yaml, playwright)
  • Added lint npm script to the root project. Running npm run lint will now run linting over all packages.
• e948750: Make npm run lint work regardless of the directory it's invoked from. Each workspace's eslint.config.mjs now pins parserOptions.tsconfigRootDir to import.meta.dirname, so parserOptions.project resolves relative to the config file's own directory rather than whichever CWD typescript-eslint happens to pick by default. Previously the six workspace configs prefixed project with the workspace directory (e.g. 'Common/tsconfig.cjs.json'), which only worked under one specific typescript-eslint version's resolution behavior and broke CI when run from within the workspace.
• Updated dependencies [113a3c1]
• Updated dependencies [c3779a5]
• Updated dependencies [0d87533]
• Updated dependencies [b16fd54]
• Updated dependencies [af7bde1]
• Updated dependencies [a7d9e91]
• Updated dependencies [e948750]
  • @epicgames-ps/lib-pixelstreamingfrontend-ue5.5@1.3.0

@epicgames-ps/lib-pixelstreamingsignalling-ue5.5@3.1.0

Minor Changes

• 5331f21: Add CORS support to the signalling web server. A new IWebServerConfig.cors option registers the cors Express middleware before the rate limiter and any route handlers, so that custom frontends hosted on a different origin can call the REST API (--rest_api) or any other route mounted on the app. Wilbur exposes this through a --cors CLI flag (default off) plus --cors_allowed_origins, --cors_allowed_methods, --cors_allowed_headers, and --cors_credentials. All four sub-options accept comma-separated values and read matching cors* keys from config.json. When --cors is set without an explicit origin list, all origins are allowed.
• 988a78c: Make the REST API reachable when Wilbur is started with --rest_api but without --serve. Previously the Express app that hosts the /api/* routes was only bound to an HTTP listener inside the serve branch, so with --serve=false --rest_api=true the listener never started and requests were answered by the WebSocket upgrade handler on the player port (426 Upgrade Required). The HTTP listener now starts whenever rest_api or serve is set. Static file serving and the homepage route are gated by a new IWebServerConfig.serveStatic flag (the port listener runs independently of static serving), and the rate limiter is registered before any route handlers so the homepage and any downstream-registered routes are all rate-limited. Wilbur logs at startup which mode it is running in.

Patch Changes

• b16fd54: - Addressing security issues raised by dependabot. (glob, js-yaml, playwright)
  • Added lint npm script to the root project. Running npm run lint will now run linting over all packages.
• e948750: Make npm run lint work regardless of the directory it's invoked from. Each workspace's eslint.config.mjs now pins parserOptions.tsconfigRootDir to import.meta.dirname, so parserOptions.project resolves relative to the config file's own directory rather than whichever CWD typescript-eslint happens to pick by default. Previously the six workspace configs prefixed project with the workspace directory (e.g. 'Common/tsconfig.cjs.json'), which only worked under one specific typescript-eslint version's resolution behavior and broke CI when run from within the workspace.
• Updated dependencies [b16fd54]
• Updated dependencies [e948750]
  • @epicgames-ps/lib-pixelstreamingcommon-ue5.5@0.3.3

@epicgames-ps/lib-pixelstreamingcommon-ue5.5@0.3.3

Patch Changes

• b16fd54: - Addressing security issues raised by dependabot. (glob, js-yaml, playwright)
  • Added lint npm script to the root project. Running npm run lint will now run linting over all packages.
• e948750: Make npm run lint work regardless of the directory it's invoked from. Each workspace's eslint.config.mjs now pins parserOptions.tsconfigRootDir to import.meta.dirname, so parserOptions.project resolves relative to the config file's own directory rather than whichever CWD typescript-eslint happens to pick by default. Previously the six workspace configs prefixed project with the workspace directory (e.g. 'Common/tsconfig.cjs.json'), which only worked under one specific typescript-eslint version's resolution behavior and broke CI when run from within the workspace.

@epicgames-ps/wilbur@2.3.0

Minor Changes

• 5331f21: Add CORS support to the signalling web server. A new IWebServerConfig.cors option registers the cors Express middleware before the rate limiter and any route handlers, so that custom frontends hosted on a different origin can call the REST API (--rest_api) or any other route mounted on the app. Wilbur exposes this through a --cors CLI flag (default off) plus --cors_allowed_origins, --cors_allowed_methods, --cors_allowed_headers, and --cors_credentials. All four sub-options accept comma-separated values and read matching cors* keys from config.json. When --cors is set without an explicit origin list, all origins are allowed.

Patch Changes

• e948750: Make npm run lint work regardless of the directory it's invoked from. Each workspace's eslint.config.mjs now pins parserOptions.tsconfigRootDir to import.meta.dirname, so parserOptions.project resolves relative to the config file's own directory rather than whichever CWD typescript-eslint happens to pick by default. Previously the six workspace configs prefixed project with the workspace directory (e.g. 'Common/tsconfig.cjs.json'), which only worked under one specific typescript-eslint version's resolution behavior and broke CI when run from within the workspace.
• 988a78c: Make the REST API reachable when Wilbur is started with --rest_api but without --serve. Previously the Express app that hosts the /api/* routes was only bound to an HTTP listener inside the serve branch, so with --serve=false --rest_api=true the listener never started and requests were answered by the WebSocket upgrade handler on the player port (426 Upgrade Required). The HTTP listener now starts whenever rest_api or serve is set. Static file serving and the homepage route are gated by a new IWebServerConfig.serveStatic flag (the port listener runs independently of static serving), and the rate limiter is registered before any route handlers so the homepage and any downstream-registered routes are all rate-limited. Wilbur logs at startup which mode it is running in.
• Updated dependencies [5331f21]
• Updated dependencies [b16fd54]
• Updated dependencies [e948750]
• Updated dependencies [988a78c]
  • @epicgames-ps/lib-pixelstreamingsignalling-ue5.5@3.1.0

@epicgames-ps/mediasoup-sdp-bridge@1.0.7

Patch Changes

• 1ff15c7: Make mediasoup-sdp-bridge importable against mediasoup-client 3.10.x ([BUG] - Mediasoup-sdp-bridge incompatible with Mediasoup >= 3.8.0 #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.