Don't override user specified depth in outdated

[G-Rath]

Restores ability to update packages using --depth as suggested by npm audit.

i.e npm update eslint-utils --depth 2.

---

I've restored the previous conditional check, which was against Infinity; however I've never worked in npm/cli before, so don't know if that value still holds water :)

How it is currently means the npm update <package> --depth <depth> commands suggested by npm audit won't work, as any depth value is clobbered to 0 if it's anything but, resulting in empty output.

This is the related community bug report.

---

Since this was included in v6.6.0 onwards, it effects all versions of Node from 11.10.0 onwards, as well as 10.16.0+

[shadowspawn]

I came across another PR related to infinity regressions which casts a little light on the original use of the infinity magic value to have different default behaviours in different commands: npm/npm#11726

(And like @G-Rath, not sure if that value is still relevant!)

[isaacs]

Thanks, this is definitely a bug.

[billatnpm]

https://docs.npmjs.com/misc/config#depth

For npm outdated, a setting of Infinity will be treated as 0 since that gives more useful information. To show the outdated status of all packages and dependents, use a large integer value, e.g., npm outdated --depth 9999

[cloakedninjas]

Seem to be experiencing this in npm 6.13.0

$ npm audit
...
found 14 vulnerabilities
....
# Run  npm update https-proxy-agent --depth 7  to resolve 9 vulnerabilities
....

npm update https-proxy-agent --depth 7
No output, a further npm audit reports the same 14 vulnerabilities

Update
Nevermind, blowing out node_modules and re-running solved the issue 🤷‍♂