Error: Premature close

Prerequisites

• I confirm my issue is not in the opened issues
• I confirm the Frequently Asked Questions didn’t contain the answer to my issue

Environment check

• I’m using the latest msw version
• I’m using Node.js version 14 or higher

Node.js version

v16.14.1

Reproduction repository

https://github.com/molvqingtai/resreq/blob/35d7e2e19d3bbbca6d4c55f5fd6119db7afdc30d/__tests__/main.spec.ts

Reproduction steps

I use Vitest test and use some Polyfill：

• node-fetch v3.2.3
• abort-controller v3.0.0
• formdata-node v4.3.2

Current behavior

When I run the test, there is a high probability that this error will occur:

 ❯ __tests__/main.spec.ts (2)
   ❯ Test methods (2)
     √ GET request
     × POST request

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  __tests__/main.spec.ts > Test methods > POST request
Error: Premature close
 ❯ NodeClientRequest.emit node:events:402:35
 ❯ NodeClientRequest.emit node_modules/.pnpm/@mswjs+interceptors@0.15.1/node_modules/@mswjs/interceptors/lib/interceptors/ClientRequest/NodeClientRequest.js:309:38
 ❯ Socket.socketCloseListener node:_http_client:423:9
 ❯ Socket.emit node:events:402:35
 ❯ TCP.<anonymous> node:net:687:12

Expected behavior

No errors

[armandabric]

I’m getting the same error with jest when upgrading from v0.36.3.

In my case:

• v0.36.3 didn’t trigger the issue (my initial version)
• v0.36.8 didn’t trigger the issue
• v0.38.0 trigger the issue
• v0.38.1 trigger the issue
• v0.38.2 trigger the issue
• v0.39.2 trigger the issue

By looking into the changelog of the v0.38.0, it could linked to the interceptor upgrade.

[lautarodragan]

I’m seeing a weird error that seems unrelated: when doing an axios.put, the request hangs forever unless I set a timeout. msw doesn’t properly track this request: it neither responds to it nor does it trigger the onUnhandledRequest.

Other http verbs seem to work fine.

I’m mentioning it here though because of @armandabric’s comment regarding versions: the issue I’m facing doesn’t happen in v0.36.8 but it happens consistently in 0.38.0 and newer versions.