allow shell commands for javascript projects (yarn/npm)

the executable type doesn’t allow to run npm/yarn commands as it expects native binaries. this is fine as long as there is a binary build artifact. in case of javascript applications there is no binary artifact. e.g. running yarn or npm requires a node or a shell binary with the executable type. so the obvious way would be to just specify this binary e.g. executable: node yarn start. unfortunately this doesn’t work as tye expects the node binary to be in the working directory.

how about extending executable to allow an executable from the path search order? or a new type which would allow to execute a shell command?

[dalibormesaric]

This actually works if you do the following

- name: front-end
  executable: cmd
  args: '/c npm run dev'

but it will work only on Windows

[onionhammer]

This seems like somewhat low hanging fruit, since this works pretty much flawlessly except that ‘executable’ is difficult to make work cross-platform; “npm” will be in different places for different OSs/versions.