You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
slavek-kucera opened this issue
Sep 29, 2023
· 1 comment
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.fsIssues and PRs related to the fs subsystem / file system.windowsIssues and PRs related to the Windows platform.
node:internal/fs/utils:350
throw err;
^
Error: ENOENT: no such file or directory, stat 'test¾_🧼utf@_8_☕'
at Object.statSync (node:fs:1690:3)
at [eval]:1:27
at Script.runInThisContext (node:vm:123:12)
at Object.runInThisContext (node:vm:299:38)
at node:internal/process/execution:82:21
at [eval]-wrapper:6:24
at runScript (node:internal/process/execution:81:62)
at evalScript (node:internal/process/execution:103:10)
at node:internal/main/eval_string:29:3 {
errno: -4058,
syscall: 'stat',
code: 'ENOENT',
path: 'test¾_🧼utf@_8_☕'
}
Additional information
It works correctly on v18.16.1
The text was updated successfully, but these errors were encountered:
richardlau
added
fs
Issues and PRs related to the fs subsystem / file system.
windows
Issues and PRs related to the Windows platform.
duplicate
Issues and PRs that are duplicates of other issues or PRs.
labels
Sep 29, 2023
duplicateIssues and PRs that are duplicates of other issues or PRs.fsIssues and PRs related to the fs subsystem / file system.windowsIssues and PRs related to the Windows platform.
Version
v18.18.0
Platform
Microsoft Windows NT 10.0.19045.0 x64
Subsystem
No response
What steps will reproduce the bug?
Create a file with 4-byte utf-8 symbol in its name e.g.
test¾_🧼utf@_8_☕
.Run
node -e "console.log(require('fs').statSync('test¾_🧼utf@_8_☕'))"
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
The existence of the file should be reported correclty. e.g.
What do you see instead?
Additional information
It works correctly on v18.16.1
The text was updated successfully, but these errors were encountered: