Composer is a dependency management tool for PHP. If you are a PHP developer, then you probably use it every day and frequently run the commands require
, install
and update
. Maybe you didn't realize it, but we can use some other Composer commands to make it easier to use.
There are many commands you can use, but today I will share 6 commands that I use and that help me every day.
Let’s talk about the show
command first. It allows you to view all installed packages for your project (including dependencies), as well as view descriptions of related packages. All this information can be found in the Composer lock file (composer.lock), but using the show
command is a relatively simpler and more convenient way to view package information.
To list all installed packages with their version numbers and descriptions, just use show
:
composer show
Sometimes this information is presented in the form of a dependency tree It will be easier to understand if you view it. You can pass --tree
or -t
Parameters:
composer show -t
If you want to filter the returned packages, you can use wildcards to pass an extra character String parameters *
:
composer show 'symfony/*'
This will return all installed symfony packages. Pay attention to the quotation marks here. If you are using the bash shell, you do not need to add these quotation marks, but if you are using zsh and you do not need the quotation marks, a ‘no matches found’ error will be reported.
If you want to see information about a specific package, the full package name is required:
composer show laravel/framework
This will show you the version installed, its license and dependencies, and where it is installed locally and other information.
If you want to know why a specific package is installed, you can use the why command to determine which dependencies require it:
composer why vlucas/phpdotenv
why
why is an alias for the depends command, but personally I find it easier to remember using 'why'. You can view this information in a dependency tree using the --tree
or -t
flag:
composer why vlucas/phpdotenv -t
Sometimes, one or Multiple installed packages will prevent the package from being installed or updated. In order to check which installation packages we can use the why-not
command (alias prohibits
). For example, Laravel recently released a new 5.8 version of the framework; we can use the why-not
command to check for any packages that are preventing us from updating the laravel/framework
package:
composer why-not laravel/framework 5.8
Similarly, we can view this information in the dependency tree using the --tree
or -t
tags:
composer why-not laravel/framework 5.8 -t
at Before using the composer update
command, you may want to check the installed packages to see which ones can be upgraded. This can be done using the outdated
command.
composer outdated
This command is one of the aliases of composer show -lo
.
According to the semantic version, color code is returned to indicate the status of each package:
If you want to highlight minor upgrades, you can use outdated
command, with --minor-only
or -m
Parameters:
composer outdated -m
I find myself using # all the time ##install,
update command parameters
--prefer-source to handle source code installation dependencies. Then, if I modify any of these dependencies, I need a way to quickly check which packages have been modified. The
status command provides a convenient method.
--verbose or
-v parameters to view locally modified packages and files:
composer status -v
licenses command for querying the complete list of licenses:
composer licenses
composer usage tutorial column!
The above is the detailed content of Recommend six little-known Composer commands. For more information, please follow other related articles on the PHP Chinese website!