René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Missing reference (and types) for `response.socket.server`","articleBody":"### Affected URL(s)\n\nhttps://nodejs.org/dist/latest-v18.x/docs/api/http.html#responsesocket\n\n### Description of the problem\n\nThere seems to have been a missing property in the API reference (and @types/node typings) regarding the `server` property of a ServerResponse instance.\r\nI have seen about it multiple times in articles or videos, for example to set up [Socket.io in Next.js](https://betterprogramming.pub/socket-io-and-nextjs-build-real-time-chat-application-part-1-976555ecba) or a [WebSocket module in Nuxt](https://www.youtube.com/watch?v=x9P4pJYCwgY).\r\n\r\nHere is a simple snippet that allows to access the `server` property:\r\n```javascript\r\nconst { createServer } = require('http');\r\n\r\ncreateServer((req, res) =\u003e {\r\n    console.log(res.socket.server); // Logs the server instance\r\n});\r\n```\r\n\r\nI 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.","author":{"url":"https://github.com/purplnay","@type":"Person","name":"purplnay"},"datePublished":"2023-03-18T15:07:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/47148/node/issues/47148"}