@ricardomat, awesome. You're welcome.
@barry-hamilton, @Ricale-Kincheski, @k8nr, @marcelo-muller, @Moacir-Vilela-Sêga, thank you for reporting the problem. I do see I had a problem in the logs. I'm looking into it now.
@mark-hollis, thanks. I thought I had it fixed this morning and found out just recently it went down again. Working on it again now.
@riccardo-cereser, please try adding this to your script:
That way you can specify the full path to your script in the commands.json file, and when your script runs, it will cd to the directory where your script is.
@russ goodness! I rest easy knowing that there is no need to log in or issue any commands.
@renan-hugo, please try this:
Run which gulp to get the path to the gulp command. Like this:
Then make your shell script something like this:
For some reason you need to specify the full path to the executables you install via npm i -g. That's been my experience on Mac anyways.
If that doesn't work, please try running the gulp script like this:
Or even like this:
To do that last one, you'll need the full path to your node executable which you can find with this command:
No one has replied