Closed nomagick closed 3 years ago
This issue was encountered on an Electron App (electron 11.2.1) on Windows 10.
Creating a user with the same name yuan'qian'wen
would reproduce this issue.
Same thing happends to both Electron and Node.
I might be wrong, but I think you env variable is actually C:\Users\YUAN'Q~1\AppData\Local\Temp
, and Node.js is returning the "correct" value. Try echo %TEMP%
in CMD, I think it should display the same string.
I might be wrong, but I think you env variable is actually
C:\Users\YUAN'Q~1\AppData\Local\Temp
, and Node.js is returning the "correct" value. Tryecho %TEMP%
in CMD, I think it should display the same string.
echo %TEMP%
indeed returns C:\Users\YUAN'Q~1\AppData\Local\Temp
.
Not a node.js issue then, sorry...
What steps will reproduce the bug?
process.env['TEMP'] === 'C:\Users\YUAN'Q~1\AppData\Local\Temp';
Which is INCORRECT.
It should be
C:\Users\yuan'qian'wen\AppData\Local\Temp
How often does it reproduce? Is there a required condition?
The windows user name be
yuan'qian'wen
;User name
bizarre'a'b'c
does not reproduce this issue;What is the expected behavior?
process.env['TEMP'] ===
C:\Users\yuan'qian'wen\AppData\Local\Temp
;What do you see instead?
Additional information