Bypassed requests made to the firebase emulator result in a timeout

[rdjpalmer]

Describe the bug

Bypassed requests made to the firebase emulator result in a timeout.

Environment

• msw: 0.27.0
• nodejs: 15.0.1
• npm: 7.0.3
• jest: 26.0.1

To Reproduce

See repro case

Expected behavior

Requests made to the firebase emulator should bypass msw entirely, and succeed.

Additional information

I've tried also supplying handlers which should still result in msw being bypassed, per #234 (comment).

Might be that this is tied to #414.

[matt-kinton]

I'm also seeing the same problem. I got around it temporarily with this which very clean haha.

const realResponseResolve = async (req: any, res: any, ctx: any) =>
    res(ctx.json(await ctx.fetch(req).then((res: Response) => res.json())));

export const testServer = setupServer(
    rest.get('*/*', realResponseResolve),
    rest.post('*/*', realResponseResolve),
    rest.put('*/*', realResponseResolve),
    rest.patch('*/*', realResponseResolve),
    rest.delete('*/*', realResponseResolve),
    rest.options('*/*', realResponseResolve)
);

[marcosvega91]

Hi @rdjpalmer, we are sorry that you're facing this issue. This is caused by streams used by firestore. I have created a PR with issue #602. A temporary workaround is to comment these lines

msw/src/mockServiceWorker.js

Lines 120 to 134 in ec64cdd

	sendToClient(client, {
	type: 'RESPONSE',
	payload: {
	requestId,
	type: clonedResponse.type,
	ok: clonedResponse.ok,
	status: clonedResponse.status,
	statusText: clonedResponse.statusText,
	body: clonedResponse.body === null ? null : await clonedResponse.text(),
	headers: serializeHeaders(clonedResponse.headers),
	redirected: clonedResponse.redirected,
	},
	})
	}

if you are not using lifecycle-events

[matt-kinton]

@marcosvega91 I don't think this works for setupServer?

[marcosvega91]

I didn't see that the issue was for setupServer. I have updated now my PR and it seems fixed for the browser. I'll check on node what is happening

[marcosvega91]

I have opened a PR here that should resolve this issue

[marcosvega91]

It's the case to leave the issue opened until node-request-interceptor is updated in msw?

[kettanaito]

@marcosvega91, let's leave it closed, update NRI, and then let the users test it out.

[rdjpalmer]

@marcosvega91 thanks for looking into this so quickly. Much appreciated. I'll test the fix out as soon as I get a chance

[rdjpalmer]

It's taken me awhile, but I've finally tested the fix. Works a treat, thanks @marcosvega91!