Version
v22.3.0 or later (v22.11.0, v23.1.0)
Platform
Microsoft Windows NT 10.0.26100.0 x64
Subsystem
No response
What steps will reproduce the bug?
$ node -v
v22.13.0
zzmn4@BOOK-CA0L9TAULR MINGW64 ~/desktop/2025/baekjoon (master)
$ node test.js
hello!!
zzmn4@BOOK-CA0L9TAULR MINGW64 ~/desktop/2025/baekjoon (master)
$ cd 백준
zzmn4@BOOK-CA0L9TAULR MINGW64 ~/desktop/2025/baekjoon/백준 (master)
$ node test.js
# ❌ No output, Node.js fails silently
zzmn4@BOOK-CA0L9TAULR MINGW64 ~/desktop/2025/baekjoon/백준 (master)
$ nvm use 20.18.1
Now using node v20.18.1 (64-bit)
zzmn4@BOOK-CA0L9TAULR MINGW64 ~/desktop/2025/baekjoon/백준 (master)
$ node test.js
hello test!
# ✅ Works fine
Node doesn't work when the folder name is in Korean
How often does it reproduce? Is there a required condition?
Every time. 100%
What is the expected behavior? Why is that the expected behavior?
before version v22.2.0, it's OK.
What do you see instead?
Node.js downgrade
Additional information
#54991
#55015
Version
v22.3.0 or later (v22.11.0, v23.1.0)
Platform
Subsystem
No response
What steps will reproduce the bug?
Node doesn't work when the folder name is in Korean
How often does it reproduce? Is there a required condition?
Every time. 100%
What is the expected behavior? Why is that the expected behavior?
before version v22.2.0, it's OK.
What do you see instead?
Node.js downgrade
Additional information
#54991
#55015