Response statusCode in node:http; undefined in Deno, 200 in Node

[vrugtehagel]

> deno --version
deno 1.43.6 (release, aarch64-apple-darwin)
v8 12.4.254.13
typescript 5.4.5
> node --version
v21.7.3

This issue popped up when trying to use Eleventy with Deno (see 11ty/eleventy-dev-server#78). To reproduce a stripped-down version of the issue, consider the following script:

import { createServer } from 'node:http'

const server = createServer((request, response) => {
    console.log(response.statusCode);
    response.end()
});

server.listen(8080);
await fetch('http:https://localhost:8080/')
server.close()

When running this script in node (e.g. node script.js), this logs 200. However, when running it in Deno (e.g. deno run -A script.js), it logs undefined. This causes the Eleventy bug mentioned above.

After a little bit of digging, I did notice that Node seems to set statusCode to 200 by default. Deno seems to set it, but after the callback provided to createServer() has already run.

A potential solution could be to default statusCode to 200 in Deno as well, though I have not checked for potential side effects as of yet.

[vrugtehagel]

Here's a slightly simpler reproduction case:

import { ServerResponse, ClientRequest } from 'node:http'

const request = new ClientRequest()
const response = new ServerResponse(request)
console.log(response.statusCode)

request.on('error', () => {})

I did try and set up Deno locally to see the impact of setting it to 200 by default, but I didn't quite manage to get the unit_node tests to run properly (24 of them fail even without making any changes). But, at least setting it to 200 by default doesn't seem to change the number of failing tests 😉