Upgrade testmode interceptors to 0.45.9 (#100585)
## Summary Upgrade the interceptor vendored for experimental test mode from `0.42.6` to `0.45.9` and regenerate its bundle. Leave the separate interceptor dependency pulled in by MSW unchanged. The old bundle can crash Node with `SIGSEGV` when an HTTPS keep-alive socket receives two mocked responses with `Content-Length`, then switches to real socket passthrough. The first fixed upstream release was `0.45.6` ([mswjs/interceptors#851](https://github.com/mswjs/interceptors/pull/851)); `0.45.9` also includes subsequent socket and HTTP fixes. The affected dependency entered Next.js in `16.3.0-canary.98` via #96059. ## Verification - Existing `test/e2e/testmode/testmode.test.ts`: all 16 tests passed in each of `test-dev-turbo`, `test-dev-webpack`, `test-start-turbo`, and `test-start-webpack`. - Local Next.js-level A/B reproduction using a route handler, test proxy, and loopback HTTPS server: two mocks followed by true passthrough using Next's internal request marker. Substituting the base revision's exact `0.42.6` bundle reproduced `SIGSEGV` on Node 24.14.0; the `0.45.9` bundle passed with the same socket reused. The upgraded fixture passed in all four modes above and on Node 24.14.0. This temporary fixture is not included in the PR. - Standalone checks passed on Node 20.20.2 and 24.14.0 for TLS keep-alive reuse, per-request authentication headers, response event counts, and abort recovery. <!-- NEXT_JS_LLM -->
Showing
This source diff could not be displayed because it is too large.
You can
view the blob
instead.
Please
register
or
sign in
to comment