7

When I do on my terminal: npm outdated -g I get a list of global packages that have updates available, and that's fine:

Package              Current  Wanted  Latest  Location
create-next-app       10.0.3  10.0.4  10.0.4  global
eslint-plugin-react   7.21.5  7.22.0  7.22.0  global
firebase-tools         9.0.1   9.1.0   9.1.0  global

After I installed all of them, I wanted to make sure that I got all the packages updated, so I hit again, the same command, but accidentally hit npm outdated -g\. This time I got a package that not listed before:

Package                 Current  Wanted  Latest  Location
eslint-plugin-flowtype    3.9.1  3.13.0   5.2.0  global

I hit again npm outdated -g and got no result, and repeated with backslash and got this package.
I checked this and didn't see anything related. Does anyone know what's the issue? Of course I can see that this eslint-plugin-flowtype package have breaking changes (3.x vs 5.x), but how is it not displayed in the original npm outdated -g command?

Thanks.

Or Assayag
  • 5,662
  • 13
  • 57
  • 93
  • 1
    This question is not programming related. You ought to ask at other fora. – kometen Jan 01 '21 at 10:00
  • 2
    Well, I think it is. – Or Assayag Jan 01 '21 at 10:03
  • 1
    So where exactly is the code that is not performing as expected. Command line issues pulling down packages is *not* programming. – kometen Jan 01 '21 at 10:06
  • npm cli commands related to programming. You can see tons of questions in SO related theses commands. Search 'npm command'. I suggest you remove the close vote. – Or Assayag Jan 01 '21 at 10:08
  • 1
    Then show the code you are having problems with. – kometen Jan 01 '21 at 10:09
  • This community is not about bugs only, but to understand processes, and commands, and things related to programming. I would appreciate if you would stop right here. Happy new year. – Or Assayag Jan 01 '21 at 10:12

1 Answers1

0

As shown in the docs, npm outdated defaults to a depth of 0, so unless you override that, you'll always be seeing only top-level dependencies that are outdated. You can run something like npm outdated --depth 9999 to see all.

Yair Cohen
  • 2,032
  • 7
  • 13