[BUG] "command not found" when running script with bash as script-shell on Windows about run-script

[schmidtk]

Confirmed on Windows 10 with Git Bash, and npm's script-shell set to use bash.

The script generated by run-script uses a Windows-style path, and the single backslashes are treated as escape characters by Git Bash. This causes the separators to be dropped from the path, and the script fails to run with "command not found" due to the invalid path.

As noted, npm 8.12.2 works as it uses an older version of run-script. Our team is using npm workspaces, which presented another problem when sub-dependencies (@semantic-release/npm in our case) depend on npm. The sub-dependency was hoisted to <project>/node_modules/npm which was used by npm run scripts in <project>/package.json.

Our current workaround to the above problem is to add [email protected] as a direct dependency of our project, so that version will be hoisted to the root node_modules. A complete solution would require updating run-script to escape the path properly in this environment.