NPM issues on Windows 10

[22ispencer]

i recently reconfigured neovim to use mini.deps instead of lazy however when i tried to update my config on windows mason can no longer find npm with the error npm.cmd failed with exit code 127 and signal 0. i did some digging and found some previous errors related to this one, however they seemed mostly fixed. i nonetheless followed all of the debugging steps from them leading me to run a healthcheck on mason. this gave me an extended error

- WARNING npm: not available
  - ADVICE:
    - spawn: npm.cmd failed with exit code 127 and signal 0. fish: Unknown command: npm.cmd
      fish: 
      npm.cmd --version
      ^~~~~~^

that's weird, does anyone know why it would be using the fish shell when i start neovim from pwsh.exe (where.exe nvim -> C:\Users\MY_USER\scoop\shims\nvim.exe), i do have wsl installed and i use fish on there but that shouldn't leak into my powershell commands (i think). any help would be greatly appreciated

[22ispencer]

I figured out the issue after realizing poetry run python was also trying to run WSL, turns out that the archwsl package from scoop updated my COMSPEC to be the shim to arch.exe. This made programs other than Windows Terminal use arch as my default shell or whatever it's called on windows.