"request" in worker.events.on('response:mocked') is always null

[kettanaito]

Discussed in #1991

^{Originally posted by canrozanes January 22, 2024}
Hi,

I was following the docs on life-cycle events and I was trying to assert on a response after making an API call.

I have the following piece of code that saves all the requests so that I can assert on the responses later.

// QUnit  setup
hooks.beforeEach(async function (this: TestContextWithMsw) {
    this.worker = setupWorker(...handlers);
    this.worker.events.on('response:mocked', ({ request, requestId, response }) => {
      this.handledRequests.push({ request, requestId, response });
    });
});

I can clearly see that MSW sends a response in the browser network tab but when I add a debugger inside the 'response:mocked' callback, I see that all the request are null.

What could I be missing?

[kettanaito]

I'd start here:

msw/src/browser/setupWorker/start/createResponseListener.ts

Lines 49 to 53 in 396b12f

	/**
	* @todo @fixme In this context, we don't know anything about
	* the request.
	*/
	request: null as any,

And figure out why we don't know anything about the request.

[kettanaito]

Opened a fix at #1993

[kettanaito]

Released: v2.1.5 🎉

This has been released in v2.1.5!

• 📄 Release notes
• 📦 npm package

Make sure to always update to the latest version (npm i msw@latest) to get the newest features and bug fixes.

---

Predictable release automation by @ossjs/release.