Linux binary install via NPM no longer works with Spago 0.7

[Dretch]

With Spago 0.6.4, on Linux, there was a binary installed at node_modules/.bin/spago, but with Spago 0.7.2 there is not.

I'm not sure exactly why this issue occurs, but I guess it is related to #121

[f-f]

Hi @Dretch, thanks for the report!

#121 is indeed the most recent change affecting this, and this week I noticed that Windows install sometimes doesn't work.
However, both on my macOS and my NixOS machines running npm install spago does indeed create a binary in node_modules/.bin/spago

Which distro are you on? And which version of npm?

[GoNZooo]

Doesn't work here either; Windows, yarn v1.12.3, so this doesn't seem like a Linux issue, exactly.

[f-f]

@GoNZooo I think the Windows issue is a different one, it looks like the release archive might be corrupted on some systems (I've seen both the cases happen). In fact, are you able to decompress the release archive for Windows by hand?

[GoNZooo]

In fact, are you able to decompress the release archive for Windows by hand?

Yes, decompressed without issue with 7zip and executed fine.

[Dretch]

I have found my problem: it is a bug with Yarn: yarnpkg/yarn#3421

I think it worked with 0.6.4 because the file being symlinked already existed (as a stub) whereas with 0.7.0 the file gets created by the preinstall script (which Yarn runs after creating the bin symlinks).

Workarounds:

• Run yarn --check-files
• Use npm

[f-f]

@Dretch oh wow, great catch! 😮 👏

I think we could bring back the stub, since it looks like the linked bug is not likely to get fixed.

@GoNZooo does it work for you if you use npm?

[GoNZooo]

@GoNZooo does it work for you if you use npm?

No, it fails with the following error, actually highlighting the issue, I guess. There's no error at all (just silent failure) with yarn.

npm ERR! path [...]\node_modules\spago\spago.exe
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '[...]\node_modules\spago\spago.exe'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

[f-f]

@GoNZooo great, this is also the failure I've seen happening on Windows.
In my case though we weren't able to extract the file. However, we didn't try 7z, which makes me think that the cause could be 7z's tar implementation (which we use to pack the archive here) being different from node-tar's implementation (which we use to unpack the archive here)