Node.js Version
v24.19.0
NPM Version
Not used (Node.js core API question); npm version not checked.
Operating System
macOS (Darwin); exact OS version not included.
Subsystem
fs
Description
In Node.js v24.19.0 with --permission enabled, legacy fs.fsyncSync/fs.fsync reject with ERR_ACCESS_DENIED. Is fsPromises.open on an explicitly allowed path, using O_CREAT|O_EXCL|O_WRONLY|O_NOFOLLOW, followed by sync() on that same returned FileHandle, an intentionally supported public route? Please identify the exact v24.19.0 test or introducing change that establishes this contract, including denied-path behavior and FileHandle ownership constraints. We are asking for the supported contract, not a way to bypass the legacy guard.
Minimal Reproduction
This is a supported-contract clarification, not a report of a FileHandle.sync() test. The proposed FileHandle route has not been executed. Please confirm whether the explicitly allowed open -> same returned FileHandle.sync() route is intentionally supported under the Permission Model, and point to the exact-version test or introducing change.
Output
ERR_ACCESS_DENIED from the legacy fsync guard with --permission enabled. No FileHandle.sync() runtime output is available because that route has not been tested.
Before You Submit
Node.js Version
v24.19.0
NPM Version
Not used (Node.js core API question); npm version not checked.
Operating System
macOS (Darwin); exact OS version not included.
Subsystem
fs
Description
In Node.js v24.19.0 with --permission enabled, legacy fs.fsyncSync/fs.fsync reject with ERR_ACCESS_DENIED. Is fsPromises.open on an explicitly allowed path, using O_CREAT|O_EXCL|O_WRONLY|O_NOFOLLOW, followed by sync() on that same returned FileHandle, an intentionally supported public route? Please identify the exact v24.19.0 test or introducing change that establishes this contract, including denied-path behavior and FileHandle ownership constraints. We are asking for the supported contract, not a way to bypass the legacy guard.
Minimal Reproduction
This is a supported-contract clarification, not a report of a FileHandle.sync() test. The proposed FileHandle route has not been executed. Please confirm whether the explicitly allowed open -> same returned FileHandle.sync() route is intentionally supported under the Permission Model, and point to the exact-version test or introducing change.
Output
ERR_ACCESS_DENIED from the legacy fsync guard with --permission enabled. No FileHandle.sync() runtime output is available because that route has not been tested.
Before You Submit