Closed Inventsable closed 3 years ago
Just hit the same problem - tar fails npm on Win10 (both cmd and PS):
PS D:\jsxbin.local> tar -xzf esdebugger-core.tar.gz
fails with:
esdebugger-core/mac/Frameworks/esdcore.framework/Resources: Can't create '\\\\?\\D:\\jsxbin.local\\esdebugger-core\\mac\\Frameworks\\esdcore.framework\\Resources'
esdebugger-core/mac/Frameworks/esdcore.framework/esdcore: Can't create '\\\\?\\D:\\jsxbin.local\\esdebugger-core\\mac\\Frameworks\\esdcore.framework\\esdcore'
esdebugger-core/mac/Frameworks/esdcore.framework/Versions/Current: Can't create '\\\\?\\D:\\jsxbin.local\\esdebugger-core\\mac\\Frameworks\\esdcore.framework\\Versions\\Current'
esdebugger-core/mac/Frameworks/esdcore.framework/Versions/A/Resources/adobe_caps.framework/Resources: Can't create '\\\\?\\D:\\jsxbin.local\\esdebugger-core\\mac\\Frameworks\\esdcore.framework\\Versions\\A\\Resources\\adobe_caps.framework\\Resources'
esdebugger-core/mac/Frameworks/esdcore.framework/Versions/A/Resources/adobe_caps.framework/adobe_caps: Can't create '\\\\?\\D:\\jsxbin.local\\esdebugger-core\\mac\\Frameworks\\esdcore.framework\\Versions\\A\\Resources\\adobe_caps.framework\\adobe_caps'
esdebugger-core/mac/Frameworks/esdcore.framework/Versions/A/Resources/adobe_caps.framework/Versions/Current: Can't create '\\\\?\\D:\\jsxbin.local\\esdebugger-core\\mac\\Frameworks\\esdcore.framework\\Versions\\A\\Resources\\adobe_caps.framework\\Versions\\Current'
tar.exe: Error exit delayed from previous errors.
One workaround would be to:
jsxbin.local
"postinstall": ""
esdebugger-core.tar.gz
to replace it with esdebugger-core
folder.npm install jsxbin.local
esdebugger-core.tar.gz
contains folders named with colon (like Resources:
or esdcore:
, see errors in my previous comment) which are treated specially on Windows, see https://superuser.com/questions/730408/how-to-extract-tar-file-on-windows-when-the-filenames-include-a-colon.
I've got the same problem. The tar file contains the symlinks for the mac directories, but the windows tar command does not support this symlink handling.
Suggested solutions:
Another workaround is to use something like Cygwin to run the installation instead of running it in Windows by itself. That's what I was using when developing the original PR.
And yep it looks like @MikolajZuzek has the best solution. We just need to create a new archive that's windows-specific and update the postinstall
scripts to call the proper one.
Fixed in #22
Hello. I've installed this previously with no issue back when it was still using the ESTK, and recently came to revisit it but get an error when running
npm install jsxbin
:Noticeably looks like it's trying to grab or do something with a Mac file structure and isn't reading my OS prior to know I'm using Windows. Any workaround to this?