This repository was archived by the owner on Apr 22, 2023. It is now read-only.

Description
OS: Windows Server 2008 R2
Node: v0.8.0
Node.js v0.8.0 cannot run applications that reside on a UNC share. The same problem applies to resolving modules that reside on a UNC share through require.
Repro:
c:
mkdir \repro
cd \repro
echo console.log('Success'); > server.js
net share uncrepro=c:\repro /grant:Everyone,Read
node \\%COMPUTERNAME%\uncrepro\server.js
Expected:
Actual:
fs.js:520
return binding.lstat(pathModule._makeLong(path));
^
Error: ENOENT, no such file or directory 'c:\TJANCZUK-HP'
at Object.fs.lstatSync (fs.js:520:18)
at Object.realpathSync (fs.js:1025:21)
at tryFile (module.js:142:15)
at Function.Module._findPath (module.js:181:18)
at Function.Module._resolveFilename (module.js:336:25)
at Function.Module._load (module.js:280:25)
at Module.runMain (module.js:487:10)
at process.startup.processNextTick.process._tickCallback (node.js:244:9)
(where TJANCZUK-HP is your machine name, same as %COMPUTERNAME%).
The actual scenario I am trying to achieve is running node.js applications from a location in the file system that is a symlink to an UNC location. It appears that the inability to run apps from UNC paths is preventing this, but once that issue is addressed, it would be good to validate that there are no additional issues in the "symlink to UNC path" scenario.