-
Notifications
You must be signed in to change notification settings - Fork 30.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v22.3.0 Cannot start if the Folder or Script File Name is Unicode. #54991
Comments
I can't reproduce with Node.js 22.9.0
|
node v22.9.0 on Windows 10/11 can not start if folder is Unicode. Our PC, Japanese Code Page 932 is selected.
|
@nodejs/platform-windows |
FWIW I can't reproduce on MacOS (I know this was reported against windows): $ echo "console.log('Tada')" > 現在のコード\ ページ/file.js
$ node 現在のコード\ ページ/file.js
Tada |
This looks like another regression of #54991 (or similar changes) |
Sorry for being late. I tested it with the following version, but it didn't work. node v22.10.0-x64 node v22.3~22.11, ~v23.1 did not work. only work on node v22.2 or before Please re-open this issue. |
We reproduce with node v22.3~v22.11 and v23.1. Windows batch file: chcp 932
echo console.log^('It works!', process.version^);> 日本語.js
node 日本語.js
echo exit code: %errorlevel% ... NG
nodes\node-v22.02 日本語.js
echo exit code: %errorlevel% ... OK
nodes\node-v22.03 日本語.js
echo exit code: %errorlevel% ... NG
nodes\node-v22.11 日本語.js
echo exit code: %errorlevel% ... NG
nodes\node-v23.01 日本語.js
echo exit code: %errorlevel% ... NG
del 日本語.js |
Version
v22.3.0 or later (v22.11.0, v23.1.0)
Platform
Windows 10
Windows 11
Subsystem
No response
What steps will reproduce the bug?
We can start normal.
Cannot start if the folder is Unicode.
-1073741819 means File System error.
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?
Additional information
Node.js blog - 2024-06-11, Version 22.3.0 (Current)
The text was updated successfully, but these errors were encountered: