Module fails when running on Windows environment from Mac OS file system

[ghost]

Scenario: Windows VM (on Mac OS host) in Powershell running this module. The files it is running on are shared to the VM from the Mac OS (HFS+) filesystem. The module makes the wrong decision about what to do and fails every time. Error below:

Build failed.

EISDIR, illegal operation on a directory 'Y:\main\Presentation\PWS\Scentsy-cli\Checkout\app\index.html'
Error: EISDIR, illegal operation on a directory 'Y:\main\Presentation\PWS\Scentsy-cli\Checkout\app\index.html'
at Error (native)
at Object.fs.symlinkSync (fs.js:848:18)
at symlinkWindows (Y:\main\Presentation\PWS\Scentsy-cli\Checkout\node_modules\ember-cli\node_modules\symlink-or-copy

\index.js:90:16)

The reason for the failure is because it's performing a Windows operation on HFS+ based files.

[stefanpenner]

At this time we don't offer support for arbitrary cross OS file mounts. If enough people need it, we may explore it further.

[izukingz]

I got this same issue on a windows machine (XP.. i know). looking into it it appears that symlink-or-copy module sees the temporary folder ending with a .tmp as a file. i tried to bypass this but hit other issues with the naming of the folder.