Confusion about composer outdated --direct
not showing any output for an outdated package
#10711
-
Hi 👋🏼 , I seem to not understand how this command is supposed to work. I assumed when I have an direct outdated version in composer.json (or .lock?), it will show me? In the example below I install Laravel ^8 but there's already ^9 available, but the command does not show anything
Testing again:
Note that "non --direct" outdated dependencies are shown:
Do I misinterpret how If so: what is the proper procedure to tell me I've outdated root dependencies? Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Well, in your case, the only direct dependency you have is Bt default |
Beta Was this translation helpful? Give feedback.
Well, in your case, the only direct dependency you have is
laravel/framework
. And the non-filteredcomposer outdated
does not showlaravel/framework
as an outdated package, which is why--direct
does not show anything.Bt default
composer outdated
takes the platform into account (not reporting a package as outdated if the newer version is incompatible with your platform). Maybe that's the reason why Laravel 9 is not suggested to you. There is a--ignore-platform-reqs
option to disable that filtering.