Fix test suite

[rissem]

remote: env: node: No such file or directory prevents test suite from running.

One option might be to simply change the shebang line from

#! /usr/bin/env node

to

#! /usr/local/bin/node

Not sure why node is not on the path anymore. Possibly a change introduced by El Capitan?

[rdickert]

Yup, that worked.

[rdickert]

Sorry, thought I had checked this, but this fix actually breaks syncer on linux, so live syncing is broken. Adding a symlink to node at /usr/local/bin/node pointing to /usr/bin/node on remote linux works (both testing locally on the mac and remote syncing to linux work), but it seems like it would be preferable not to add steps to the installation process.

[rdickert]

Fixed on my machine by adding export PATH=/usr/local/bin to a new file ~/.zshenv (Zshell only - more on bash below).

This post describes the behavior of zshell. Basically, if you run in non-interactive, non-login mode, .zshenv is the only startup script that will be executed (changing .zprofile did not work for me). If the description of that post is correct, bash users may not be able to set the path at all (!), but I haven't tested it so YMMV.

@rissem can you confirm if this solves it for you? If so, I can add a section to the readme about running the tests. If I do that, is there anything else about contributing that I should add?

[rissem]

Awesome! It works for me, nice detective work. And that seems like a completely reasonable thing to ask in the README.

I'd probably suggest export PATH=$PATH:/usr/local/bin just so other values aren't overwritten, but probably would work either way.