Repository navigation
fs.symlink can’t create directory symlinks on Windows #18518
Description
Activity
Can't reproduce on master.
For an idea of the context of this: ghost-cli creates a directory symlink as part of
ghost install local, and if it fails then the result is incomplete and non-functional, so it’s broken on Windows. Having WSL, I worked around that by installing ghost-cli on the Ubuntu side instead of the Windows side, but that’s a workaround rather than a fix.The libuv upgrade will make its way into node 8 eventually. Since there is nothing to do but wait I'll go ahead and close this out.
The relevant libuv PR: libuv/libuv#1706
This is still a problem. Any update?
@livingstonef I now have 8.11.1, and it’s fixed there. If you have an older version of Node, try upgrading. If it’s the same or newer, ensure your Windows installation is in Developer Mode, and then please verify that my “simplest example to demonstrate the issue” does in fact not work for you; if it does work, then you probably have a different issue.
fs.symlinkappears to require admin privileges on Windows 10 for some reason. If anyone else runs into this, try running as admin.@flotwig For historical and security reasons, it requires either admin privileges, or for the machine to be in developer mode and the appropriate flag set in the API call (and that flag was what was missing). But yeah, this was fixed over a year ago now.
Reacted by Roman HotsiyYeah, we're still using Node 8.9.3 (though upgrading soon!)
FWIW, I actually needed to pass
type=junctiontofs.symlink, that made running as admin unnecessary and made the symlinks actually work.Reacted by Daniel Camargo, YiJun, Lide, Dariusz Filipiak, Michael Jonker, Iwá, plantainX and Baptiste Clarey SjostrandReacted by IwáReacted by Iwá- added a commit that references this issue
on Apr 21, 2020 是的，我们仍在使用 Node 8.9.3（尽管很快就会升级！）
FWIW，我实际上需要传递
type=junction给fs.symlink，这使得以管理员身份运行变得不必要并使符号链接实际工作。Yeah, we're still using Node 8.9.3 (though upgrading soon!)
FWIW, I actually needed to pass
type=junctiontofs.symlink, that made running as admin unnecessary and made the symlinks actually work.There are still some problems. Folders are created correctly, but the files are also recognized as folders and the soft links created do not work.
FWIW, I actually needed to pass
type=junctiontofs.symlink, that made running as admin unnecessary and made the symlinks actually work.Still true in node v16.17.0
- added a commit that references this issue
on Aug 24, 2022 @IRod22 v18.x never had this issue. I suspect you're misunderstanding the discussion here.
fs.symlinkapi need runnning asadmin. butmklinkdon'tv18.16.0 windows 11// need admin // err.message EPERM: operation not permitted, symlink 'E:\Git\xx\i' -> 'E:\Git\xx\o' fs.symlinkSync('i', 'o')// this is ok const { execSync } = require('child_process'); execSync('mklink /J o i', { windowsHide: true });Reacted by justinlm and Matt McCormick- added 2 commits that reference this issue
on Feb 28, 2024
Using
fs.symlinkSync( x, y, 'dir' )to create a directory symlink is failing (EPERM: operation not permitted), whilemklink /dis able to make the symlink.Simplest example to demonstrate the issue:
File symlinks are fine; it’s only directory symlinks that are failing. It doesn’t matter whether the target path exists or not, it fails with the same EPERM error.
Meanwhile,