bug(windows): native command execution syntax doesn’t work for npm/npx package about fd HOT 2 OPEN

See rust-lang/rust#37519 for some history about the behaviour of Command::spawn() on Windows. One useful suggestion from that issue is the which crate, which provides command resolution behaviour that may be closer to what CMD/PowerShell actually does to resolve executables.

Which xargs implementation are you using? Never mind, I see it's from git bash

from fd.

Type: Additional information ➕

1. xargs + npx on Windows without WSL

When I run fd + npx CoffeeLint on Windows 11 without WSL, I get this output:

fd --print0 --extension coffee | xargs --null npx coffeelint
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Microsoft Store:
https://aka.ms/wslstore

I don’t reproduce this behavior on continuous integration services perhaps because CIs have WSL pre-installed.

I think that WSL — too big dependency to run npx commands, and that it would be nice if Windows users without WSL could run npx commands use fd.

2. xargs implementation

Which xargs implementation are you using?

I added this information to my AppVeyor build. Yes, I used the xargs command from Git for Windows.

I can’t resolve the WSL problem when I also use the xargs command from Cygwin 3.5.1:

where xargs
D:\Chocolatey\tools\cygwin\bin\xargs.exe

D:\Chocolatey\tools\cygwin\bin\xargs.exe --version
xargs (GNU findutils) 4.9.0
Packaged by Cygwin (4.9.0-1)
Copyright (C) 2022 Free Software Foundation, Inc.

fd --print0 --extension coffee | D:\Chocolatey\tools\cygwin\bin\xargs.exe --null npx coffeelint
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Microsoft Store:
https://aka.ms/wslstore

Thanks.

from fd.