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]

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

[ArcanisCz]

Hello, I am facing same problem - I am on Windows and I want yarn scripts to run using git bash for certain project (same as written here for yarn 1.19+ https://stackoverflow.com/questions/23243353/how-to-set-shell-for-npm-run-scripts-in-windows). I have been using similar config for npm for years.

Any chance we can get this config back OR get similar results?

[clemyan]

@ArcanisCz As mentioned above, what script are you using that Yarn's portable shell can't handle and must be run with bash? Do you have a specific example of such a script?

[jonsherrard]

@clemyan pops and pushed commands are used a lot

[clemyan]

@jonsherrard
Do you mean pushd and popd? Are those used a lot in oneliner scripts?
Instead, you can just save the cwd in a variable: ORIG_CWD=$(pwd); cd /; pwd; cd $ORIG_CWD; pwd. Anything more complicated than that should probably be a proper script file instead of a package script.

Not all shells implement pushd and popd (e.g. ash and dash don't), and not all platforms have a shell that does. So even without Yarn's portable shell, using pushd and popd in package scripts is not cross-platform. If you are writing package scripts with shell-specific stuff (e.g. bashisms), then instead of allowing it to silently fail or do unexpected stuff, you should make the script fail-fast by explicitly invoking the desired shell: bash -c '...'.

If there is actually a need for pushd and popd, we can implement those in our portable shell, which would then make them available to all users in a cross-platform manner.