fs.symlink requires administrator privileges on Windows

[lqzhgood]

Version

20.0.0

Platform

Microsoft Windows NT 10.0.22621.0 x64

Subsystem

No response

What steps will reproduce the bug?

const fs = require("fs");
fs.mkdirSync("i");

fs.symlinkSync("i", "o"); 

if run in non-elevated context cmd.exe throw Error // Error: EPERM: operation not permitted, symlink 'i' -> 'o'

run in elevated context cmd.exe by admin is ok

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

fs.symlinkSync run in non-elevated context cmd.exe is ok

mklink does not require administrator privileges to execute on Windows cmd.

What do you see instead?

Error: EPERM: operation not permitted, symlink 'i' -> 'o'`

Additional information

I found this closed issue, but the problem has not been resolved.
#18518

[bnoordhuis]

It's mentioned in the documentation: pass 'dir' to fs.symlink() to indicate you want to create a Windows directory symlink.

Node tries to auto-detect the symlink type but that's a fallible heuristic. It's better to be explicit.

[lqzhgood]

fs.symlinkSync("i", "o", "dir");

also needs to run in elevated context by admin in Windows.