fix: patch default shell on win32

[thezzisu]

Fixes #398

It's a good idea to open an issue first for discussion.

• Tests pass
• Appropriate changes to README are included in PR
• Types updated

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[thezzisu]

When using zx on a windows machine with wsl installed, this code core.ts#L74 will make base.exe the default shell and execute commands in it, which cause a lot of problems. This PR fixed that problem by skip bash check on win32 platforms.

[antonmedv]

So what is preferable shell on win? cmd.exe? What happens in running script within WSL?

[thezzisu]

On windows, the defaults.shell will be true, make node.js decide which shell to run. Normally it's cmd.exe.
See also https://nodejs.org/api/child_process.html#default-windows-shell.
If running in WSL then process.platform should be linux, and nothing other happens.
And, for a very edge case that running windows' node.exe inside WSL，it's shoud be same as running on windows normally.

[antonmedv]

It also will be cool to add test for this. Which only runs on win32 and add a GitHub workflow (on Win machine) to test this use case. Can you, please, add such test&workflow?

[thezzisu]

Ok, I'll implement the tests later.

[thezzisu]

Ok. Win32 specific test implemented and validated both locally & on gh actions.