npm outdated does not seem to check devDependecies like it used to

[dmytro-gokun]

npm -v
6.4.14

node -v
v12.18.0

[shadowspawn]

What are you seeing that has changed? It is working for me with npm 6.14.5.

You could try updating npm with

npm install -g npm@latest 

[dmytro-gokun]

Nope, updating to 6.14.5 would not help. And, funny enough, "npm -g outdated" would not tell me there were 6.14.5 available at all. That's all is weird. I guess i need to try reinstalling node/npm.

[ljharb]

@dmytro-gokun any chance ~/.npmrc, or env, has something that might be setting --only=production or similar?

[shadowspawn]

Check for only like:

$ npm config get only                                                                                                                                                 develop
null

And if it is set, to see where it came from:

npm config list  

[dmytro-gokun]

Nope. It's "null" and it's not listed. Furthermore, using flag "--dev" or even setting only="production" does not help at all. I observe this on two PCs running the latest Windows 10, node & npm.

[ljharb]

What about other config values? env vars?

[darcyclarke]

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.