This is a list of common pitfalls on using Composer, and how to avoid them.
Before asking anyone, run
composer diagnoseto check for common problems. If it all checks out, proceed to the next steps.
When facing any kind of problems using Composer, be sure to work with the latest version. See self-update for details.
Make sure you have no problems with your setup by running the installer's checks via
curl -sS https://getcomposer.org/installer | php -- --check.
Ensure you're installing vendors straight from your
rm -rf vendor && composer update -vwhen troubleshooting, excluding any possible interferences with existing vendor installations or
Package not found
Double-check you don't have typos in your
composer.jsonor repository branches and tag names.
Be sure to set the right minimum-stability. To get started or be sure this is no issue, set
Packages not coming from Packagist should always be defined in the root package (the package depending on all vendors).
Use the same vendor and package name throughout all branches and tags of your repository, especially when maintaining a third party fork and using
Package not found on travis-ci.org
Check the "Package not found" item above.
If the package tested is a dependency of one of its dependencies (cyclic dependency), the problem might be that composer is not able to detect the version of the package properly. If it is a git clone it is generally alright and Composer will detect the version of the current branch, but travis does shallow clones so that process can fail when testing pull requests and feature branches in general. The best solution is to define the version you are on via an environment variable called COMPOSER_ROOT_VERSION. You set it to
dev-masterfor example to define the root package's version as
before_script: COMPOSER_ROOT_VERSION=dev-master composer installto export the variable for the call to composer.
Need to override a package version
Let say your project depends on package A which in turn depends on a specific version of package B (say 0.1) and you need a different version of that package - version 0.11.
You can fix this by aliasing version 0.11 to 0.1:
"B": "0.11 as 0.1"
See aliases for more information.
Memory limit errors
If composer shows memory errors on some commands:
PHP Fatal error: Allowed memory size of XXXXXX bytes exhausted <...>
memory_limit should be increased.
Note: Composer internally increases the
512M. If you have memory issues when using composer, please consider creating an issue ticket so we can look into it.
To get the current
memory_limit value, run:
php -r "echo ini_get('memory_limit').PHP_EOL;"
Try increasing the limit in your
php.ini file (ex.
; Use -1 for unlimited or define an explicit value like 512M
memory_limit = -1
Or, you can increase the limit with a command-line argument:
php -d memory_limit=-1 composer.phar <...>
"The system cannot find the path specified" (Windows)
- Open regedit.
- Search for an
- Check if it contains any path to non-existent file, if it's the case, just remove them.
API rate limit and OAuth tokens
Because of GitHub's rate limits on their API it can happen that Composer prompts for authentication asking your username and password so it can go ahead with its work.
If you would prefer not to provide your GitHub credentials to Composer you can manually create a token using the following procedure:
Add it to the configuration running
composer config -g github-oauth.github.com <oauthtoken>
Now Composer should install/update without asking for authentication.
proc_open(): fork failed errors
If composer shows proc_open() fork failed on some commands:
PHP Fatal error: Uncaught exception 'ErrorException' with message 'proc_open(): fork failed - Cannot allocate memory' in phar
This could be happening because the VPS runs out of memory and has no Swap space enabled.
total used free shared buffers cached
Mem: 2048 357 1690 0 0 237
-/+ buffers/cache: 119 1928
Swap: 0 0 0
To enable the swap you can use for example:
/bin/dd if=/dev/zero of=/var/swap.1 bs=1M count=1024
如果您发现文档中有错误，或者能够帮我们完善文档，请提交到我们的 Github 仓库吧！