fix: allow sending responses with status 0

Author: wheresrhys

packages/fetch-mock/src/Route.ts

@@ -89,6 +89,12 @@ function isBodyInit(body: BodyInit | object): body is BodyInit {
 }
 
 function sanitizeStatus(status?: number): number {
+	if (status === 0) {
+		// we do this here for now because we can't construct a Response with status 0
+		// we overwrite to 0 later in the proxy wrapper around teh response.
+		return 200;
+	}
+
 	if (!status) {
 		return 200;
 	}

packages/fetch-mock/src/Router.ts

@@ -70,7 +70,7 @@ function shouldSendAsObject(responseInput: RouteResponseData): boolean {
 	// TODO improve this... make it less hacky and magic
 	if (
 		responseConfigProps.some(
-			(prop) => (responseInput as RouteResponseConfig)[prop],
+			(prop) => prop in (responseInput as RouteResponseConfig),
 		)
 	) {
 		if (
@@ -268,6 +268,11 @@ export default class Router {
 						return false;
 					}
 				}
+
+				if (responseInput.status === 0) {
+					if (name === 'status') return 0;
+					if (name === 'statusText') return '';
+				}
 				// TODO fix these types properly
 				//@ts-expect-error TODO probably make use of generics here
 				if (typeof response[name] === 'function') {

packages/fetch-mock/src/__tests__/FetchMock/response-construction.test.js

@@ -27,6 +27,13 @@ describe('response construction', () => {
 				);
 			}
 		});
+
+		it('should be able to send status 0', async () => {
+			fm.route('*', { status: 0 });
+			const res = await fm.fetchHandler('http://a.com/');
+			expect(res.status).toEqual(0);
+			expect(res.statusText).toEqual('');
+		});
 	});
 
 	describe('string', () => {