If Jigsaw is not installed globally, gulp tasks fail. about jigsaw

[adamwathan]

Hey Pete! One thing I actually have set up on my machine is to add ./vendor/bin near the beginning my $PATH, so if I'm in a project directory, locally installed tools are preferred.

It's probably not a great idea to force everyone else to do that though, so definitely open to ideas to make this just work automatically.

Could we check for the existence of ./vendor/bin/jigsaw and use that if it exists, falling back to the global install? Haven't worked with filesystem APIs in Node/Gulp before but can definitely look into it.

[petemcfarlane]

Yup, you could create a bash file, something like this, to check for existence. Not sure if it's too much of a hack though?

#!/bin/bash
if type jigsaw &> /dev/null; then
    echo jigsaw exists
elif type ./vendor/bin/jigsaw &> /dev/null; then
    sed -i '' 's|jigsaw build|./vendor/bin/jigsaw build|' gulpfile.js
    echo ./vendor/bin/jigsaw exists, updated your gulpfile.js
else
    echo jigsaw executable not found in your \$PATH
fi

[petemcfarlane]

Maybe just documenting it as something to be aware of would be cleaner?

[adamwathan]

I think we can use something like this directly in the gulpfile: https://nodejs.org/api/fs.html#fs_fs_access_path_mode_callback

Will have a play in a bit 👍

[erickpatrick]

Hi @petemcfarlane, the gulp command now is able to check whether one has a global or local version of jigsaw. Things are easier for us, now =)

[damiani]

Addressed in #85