René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Deprecate AbortSignal on resources that are not actions","articleBody":"We currently have several APIs that support AbortSignals like:\r\n\r\n - http.Server\r\n - stream.Readable / stream.Writable\r\n - child_process methods returning a child (and not a promise)\r\n - addAbortSignal\r\n\r\nThose APIs are resources and not actions and support `Symbol.dispose` `Symbol.asyncDispose`. \r\n\r\nSince they are disposables, we should deprecate support for AbortSignal on APIs that are resources and not actions (while keeping AbortSignal on APIs that are actions (e.g. return promises)) and encourage the safe helper we added for `addAbortListener` on those updating our docs.\r\n\r\nBasically instead of:\r\n\r\n```js\r\nfunction foo() {\r\n  const ac = new AbortController();\r\n  const httpServer = /* */\r\n  httpServer.listen(3000, { signal: ac.signal });\r\n \r\n  return someAsyncAction().then(() => ac.abort()); // close the server\r\n}\r\n```\r\n\r\nWe should encourage:\r\n\r\n```js\r\nasync function foo() {\r\n  using httpServer = /* */\r\n  httpServer.listen(3000);\r\n  await someAsyncAction()\r\n}\r\n```","author":{"url":"https://github.com/benjamingr","@type":"Person","name":"benjamingr"},"datePublished":"2023-07-10T12:26:51Z","url":"https://github.com/nodejs/node/issues/48725"}