feat: update the node.js version range

[mikicho]

Following this: #598 (comment)

[kettanaito]

Why skipping v21?

Also, could you give more context why we need to update the version?

[mikicho]

Because of the rawHeaders symbol change in Node.js.

Why skipping v21?

What do you mean?
This range translates to: "any version between 18.20.0 and 20, OR anything above 20.12.1"
You can play this it here

[kettanaito]

Still a bit confused. We currently don't depend on Node.js for raw headers and use our own proxy to gather them. Does the version change still apply in that case?

[mikicho]

Interesting..

const { ClientRequestInterceptor } = require('@mswjs/interceptors/ClientRequest')
const http = require('http')

const interceptor = new ClientRequestInterceptor({
  name: 'my-interceptor',
})
interceptor.apply();
interceptor.on('request', async ({ controller }) => {
  controller.respondWith(new Response(null, { headers: { 'set-cookie':  ['mocked-cookie-0;mocked-cookie-1', 'mocked-cookie-2'] }}))
});

(async function () {
   http.get('http://example.com', (res) => {
    console.log(res.headers);
   });
})()

With version 20.11.1 the output is: (Array length is 1)

{ 'set-cookie': [ 'mocked-cookie-0;mocked-cookie-1,mocked-cookie-2' ] }

With version 20.12.2 the output is: (Array length is 2, as expected)

{ 'set-cookie': [ 'mocked-cookie-0;mocked-cookie-1', 'mocked-cookie-2' ] }

[mikicho]

@kettanaito I'm closing this. I updated the version in nock instead. It may be related to the rawHeaders feature, which we will probably remove soon anyway 🎉