René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"diagnostics_channel: add a channel for filesystem operations","articleBody":"### What is the problem this feature will solve?\n\n`node:diagnostics_channel` does not currently expose a built-in channel for filesystem operations performed through `node:fs` and `node:fs/promises`.\n\nThe proposed scope is the public filesystem APIs. Calls made directly by native addons or arbitrary native code do not need to be included in this contract.\n\n### What is the feature you are proposing to solve the problem?\n\nAdd a built-in tracing channel family for filesystem operations. One possible naming scheme is:\n\n- `tracing:fs.operation:start`\n- `tracing:fs.operation:end`\n- `tracing:fs.operation:asyncStart`\n- `tracing:fs.operation:asyncEnd`\n- `tracing:fs.operation:error`\n\nThe shared event object could contain:\n\n- `operation`: a stable operation name such as `open`, `read`, `stat`, `readdir`, or `realpath`.\n- `api`: `sync`, `callback`, `promise`, `stream`, or `filehandle`.\n- Path, source/destination, or file descriptor fields when applicable, preserving the value type passed by the caller.\n- `result` and `error` following the existing `TracingChannel` conventions.\n\nLarge read/write buffers should not be copied into event metadata. The exact publication layer—public API wrappers or the lowest shared internal filesystem layer—can be determined during implementation, but the documented payload should remain independent of internal `FSReqCallback` details.\n\nUsing one operation family with an `operation` field avoids requiring wildcard channel subscriptions while allowing subscribers to filter individual operations.\n\n### What alternatives have you considered?\n\nWrapping exports from `node:fs` and `node:fs/promises` is incomplete when references have already been captured and requires synchronization with named built-in ESM exports. `async_hooks` exposes asynchronous resource lifecycles rather than stable filesystem operation semantics and does not cover synchronous calls. Trace events use a different consumption API and payload contract.\n","author":{"url":"https://github.com/mcollina","@type":"Person","name":"mcollina"},"datePublished":"2026-08-16T16:45:07Z","url":"https://github.com/nodejs/node/issues/65330"}