Use different shell for nx:run-commands executor?

[ls-bit]

We are using pnpm and have script-shell configured to use git bash on Windows. This allows us to use common bash syntax in package.json scripts even on Windows.

nx:run-commands executor seems to always use cmd.exe to run dependent tasks defined by task pipeline, which does not work with our scripts. So we would like to configure shell to use git bash.

Is there any way to configure the shell used by nx:run-commands executor?

[phaze-phusion]

Our team also use pnpm and use bash scripts everywhere. For us Nx defaults to using /bin/sh, with nowhere to configure it. We have developers on both Ubuntu and Mac. Everyone has bash installed even if they use a different shell (bash, zsh or fish). Even our CI pipelines use bash.

I've found that using /bin/bash -c "..." in the command property of nx:run-commands allows us to use bash syntax. But that requires careful escaping of quotation marks and even then it can get confusing because of JSON's own double quotation marks.

For anyone wanting to go this route here is a simple example:

"arbitrary": {
  "executor": "nx:run-commands",
  "options": {
    "commands": [
      {
        "command": "/bin/bash -c 'opt=\"some text\"; [[ $opt == \"some text\" ]] && echo true || echo false'"
      }
    ]
  }
}

[phaze-phusion]

Update:
Looking at the run-commands source, nx:run-command uses Node's child_process.exec() method which has an option to set the shell. That option just needs to be made available in the schema and passed on to the exec method.

According to NodeJS docs the shell defaults to /bin/sh on Unix, and process.env.ComSpec on Windows.

[landon-buttars-wgu]

This issue is particularly problematic for lean environments that may not have sh installed. Has there been an update since?