Affected URL(s)
https://nodejs.org/dist/latest-v18.x/docs/api/http.html#responsesocket
Description of the problem
There seems to have been a missing property in the API reference (and @types/node typings) regarding the server property of a ServerResponse instance.
I have seen about it multiple times in articles or videos, for example to set up Socket.io in Next.js or a WebSocket module in Nuxt.
Here is a simple snippet that allows to access the server property:
const { createServer } = require('http');
createServer((req, res) => {
console.log(res.socket.server); // Logs the server instance
});I don't know if that property is supposed not to be used or if it is just missing from the API references, but it seems like the common way to 'plug in' WebSocket servers onto frameworks that don't directly provide a way to do so.
Affected URL(s)
https://nodejs.org/dist/latest-v18.x/docs/api/http.html#responsesocket
Description of the problem
There seems to have been a missing property in the API reference (and @types/node typings) regarding the
serverproperty of a ServerResponse instance.I have seen about it multiple times in articles or videos, for example to set up Socket.io in Next.js or a WebSocket module in Nuxt.
Here is a simple snippet that allows to access the
serverproperty:I don't know if that property is supposed not to be used or if it is just missing from the API references, but it seems like the common way to 'plug in' WebSocket servers onto frameworks that don't directly provide a way to do so.