which sync cannot work on windows about node-which HOT 1 CLOSED

My guess is that you don't have .py in your PATHEXT environment variable. Therefor, even though esptool.py might be in the PATH, and have a mode including +x, it isn't executable because Windows systems judge executability based on the path extension. Note that if you ran esptool.py in the cmd.exe terminal, it'll say that it doesn't recognize the command.

bash on windows does not judge executability this way, since it's a ported unix tool that follows unix conventions in most things.

Put .py in your PATHEXT environment variable, and it'll work.

Or you can pass a modified pathExt by doing which.sync('esptool.py', {pathExt: ';' + process.env.PATHEXT}). That works because PATHEXT is colon-delimited, and if there's an entry at the start of it that is '', then it'll allow any command that is fully specified.

I know this is all a bit bonkers if you're more familiar with the Unix way, but it's how Windows works, and the point of this lib is to work out if exec(command) will find a thing or not, and which one it'll find.

from node-which.