First install globally on armhf installs x86_64 binary

[danwdart]

When I first do a npm -g install @dadi/cli I get a binary from the wrong architecture plonked in my bin directory. Shouldn't this either be a script or match the source arch?

Reproducing the issue, just install @dadi/cli on a Pi and notice that you get a 64-bit PC version of the dadi binary appearing.

[danwdart]

Sounds like this is the work of https://github.com/zeit/pkg
I don't think this is needed when a "bin" can just be specified in a package.json - being a js script - then it would work cross-arch and not have to include a whole other node.

[danwdart]

Oh, apparently pkg can target to armv6/armv7 too - still not sure about armv8 (pi3 with 64 bit OS)

[eduardoboucas]

We use pkg because it allows us to have automatic updates in place. When you install @dadi/cli, the JS file downloads the binary that is appropriate for your architecture. Every time you run dadi, it's able to determine whether there is a newer version of CLI available and, if so, download the new binary and replace the existing one.

It does introduce some complexity and we might decide that it's not a tradeoff worth having. Building for ARM was not a strong requirement when we started the project, so if we come to the conclusion it's not possible with pkg, we can get rid of it.

[danwdart]

It turns out it certainly is possible - just would need enabling.

[danwdart]

(For now I'm just aliasing to the index.js in a clone)