René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"vfs: statfs succeeds for nonexistent paths","articleBody":"### Version\n\nmain\n\n### Platform\n\n```text\nAll\n```\n\n### Subsystem\n\nvfs\n\n### What steps will reproduce the bug?\n\n```js\nimport fs from 'node:fs/promises';\nimport path from 'node:path';\nimport vfs from 'node:vfs';\n\nconst virtualFs = vfs.create();\nconst mountPoint = virtualFs.mount();\n\ntry {\n  console.log(await fs.statfs(path.join(mountPoint, 'missing')));\n} finally {\n  virtualFs.unmount();\n}\n```\n\n### How often does it reproduce? Is there a required condition?\n\nAlways\n\n### What is the expected behavior? Why is that the expected behavior?\n\n`fs.statfs()` should reject with `ENOENT`, matching its behavior for nonexistent paths on the native filesystem.\n\n### What do you see instead?\n\n`fs.statfs()` resolves with a synthetic VFS filesystem-statistics object even though the requested path does not exist.\n\n### Additional information\n\nfs equivalent\n```js\nimport fs from 'node:fs/promises';\nimport os from 'node:os';\nimport path from 'node:path';\n\nconst directory = await fs.mkdtemp(path.join(os.tmpdir(), 'statfs-'));\n\ntry {\n  console.log(await fs.statfs(path.join(directory, 'missing')));\n} finally {\n  await fs.rm(directory, { recursive: true, force: true });\n}\n```\n\nThis rejects with an `ENOENT` error.","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-09-01T03:18:19Z","url":"https://github.com/nodejs/node/issues/65692"}