Support for shell-script config lost with Yarn 2?

[ercgrat]

In earlier versions of yarn I relied on yarn config set script-shell <path to shell executable> to get our repo's scripts to work on windows by using git bash. This configuration option is no longer available, and I can't find an equivalent. How can I configure the default shell for Yarn 2?

[arcanis]

You currently can't, because we embed our own shell that ensures the scripts commands portability across systems.

What were you using script-shell for?

[ercgrat]

The repo I'm working in just has a lot of bash scripts in the package.json that don't work using cmd.exe on Windows. Setting script-shell on npm was not enough to get it to work in Yarn 1, you also had to set it in yarn. This was a long-term solution for me until I just upgraded us to Yarn 2.

That still seems to be the case, or perhaps I need to update some additional configuration to Yarn 2 to get the bash context to work correctly, because it seems to be getting picked up. My understanding of this is pretty limited. I'm just getting errors now related to not understanding windows filepaths, e.g.:
/bin/bash: C:\Users\ercgr\silo-technologies\silo-web\cypress\support\db\init_be.sh: No such file or directory

[ercgrat]

For context, this is what I referenced months ago to fix yarn 1:
https://stackoverflow.com/a/58188828/1113930

[merceyz]

As @arcanis mentioned we ship a shell that should handle the most common stuff on all systems, if you have something that doesn't work please open a feature request (or bug report) and we could look into fixing it.

[ercgrat]

Ok I dug into this a little more trying to reproduce for a bug report, and realized that the issue is just the shebang at the top of our script. Before, when I was able to set bash as the default, this didn't cause any issues. Now I have to run yarn starting from a bash context on Windows or I get "No such file or directory" - it was nice when yarn worked from anywhere. This something that has a chance of getting fixed if I write it up?

Specifically, this:
#!/bin/bash