ncu command conflict with Nvidia CUDA executable (ncu.exe) on Windows 10

[MI53RE]

• [ x ] I have searched for similar issues
• [ x ] I am using the latest version of npm-check-updates
• [ x ] I am using node >= 10.17

---

I have scrolled all arround but couldn't find any information on this. This happened after I wanted to update my jsreport install

Steps to Reproduce

You need to have Cuda installed on your machine and npm-check-update

On Powershell / cmd / Windows terminal just type ncu command and press enter

Current Behavior

getting this message

PS F:\Dev\jsreport> ncu
usage: ncu.exe [options] [program] [program-arguments]

General Options:
  -h [ --help ]                         Print this help message.
  -v [ --version ]                      Print the version number.
  --mode arg (=launch-and-attach)       Select the mode of interaction with the target application:
                                          launch-and-attach
                                          (launch and attach for profiling)
                                          launch
                                          (launch and suspend for later attach)
                                          attach
                                          (attach to launched application)
[...]
  --clock-control arg (=base)           Control the behavior of the GPU clocks during profiling. Allowed values:
                                          base
                                          none
  --nvtx-include arg                    Adds include statement to the NVTX filter, which allows selecting kernels to
                                        profile based on NVTX ranges.
  --nvtx-exclude arg                    Adds exclude statement to the NVTX filter, which allows selecting kernels to
                                        profile based on NVTX ranges.

Sampling Options:
  --sampling-interval arg (=auto)       Set the sampling period in the range of [0..31]. Actual frequency is 2 ^ (5 +
                                        value) cycles. If set to 'auto', the profiler tries to automatically determine
                                        a high sampling frequency without skipping samples or overflowing the output
                                        buffer.
  --sampling-max-passes arg (=5)        Set maximum number of passes used for sampling.
  --sampling-buffer-size arg (=33554432)
                                        Set the size of the device-sided allocation for samples in bytes.

(not logging everything as it is just the manual of ncu.exe)

Expected Behavior

As this is IMO more related to the OS way of resolving path, I would say the only "fix" possible is to include this case into the documentation so users are aware the 2 tools could enter in conflict (CUDA being not foreign to NodeJs)

Everything work fine if using the npm-check-update command

[raineorshine]

Thanks for the tip. I added this to the README:

• If ncu prints output that does not seem related to this package, it may be conflicting with another executable such as ncu-weather-cli or Nvidia CUDA. Try using the long name instead: npm-check-updates.

[teadrinker2015]

Little suggestion: Maybe it's better to place it rghit after the first example of the Usage paragraph. I'm not an English native speaker, which caused me not realizing that huge help message comes from another program. It was only until I made a lot of dumb investigations and finally confused about the massage "unrecognised option '--packageFile'", that I found what I was doing TAT