• Fixes a transitive High severity dependency in path-to-regexp

TLDR:
The solution is to either:

1. set testEnvironment: 'node' in the Jest config
2. Polyfill the Web Streams API in JSDOM

option 1 is not possible because the current tests require access top the DOM

AI explanation of issue:

What changed between versions 2.3.5 and 2.5.0 that might cause TransformStream errors in Jest?

Several changes shipped in MSW’s version 2.5.x. One of the notable changes was more thorough usage of the Web Streams API (which includes classes like TransformStream). The Web Streams API is natively available in modern browsers and in newer versions of Node.js (≥ 18). In older environments (or certain test runners), the TransformStream global may not exist by default, leading to the error:

ReferenceError: TransformStream is not defined

Why does this happen in Jest?
•Jest’s default test environment (which is often jest-environment-jsdom) may not include the TransformStream global.
•If you’re using an older version of Node.js (like Node 14 or 16) along with Jest, you may also be missing the global Web Streams classes.

As of MSW 2.5.x, the library expects TransformStream (and possibly other parts of the Web Streams API) to be present. If it’s not, you’ll see the ReferenceError.

Even though you’re on Node 20 (which natively supports the Web Streams API), you can still get ReferenceError: TransformStream is not defined if your test environment (usually JSDOM in Jest) doesn’t expose the TransformStream global. In other words, Node itself may have TransformStream, but JSDOM (or another test environment) might not.