Composer doesn’t have a feature to automatically run self-update to my knowledge. Also, running self-update by itself doesn’t seem like the right way. Maybe you don’t have permission? Then try using sudo, like: sudo composer self-update. It is just a simple command, and you should only need to do it once about every 30 days. … Read more
Lets look at composer why or composer depends command. This command shows which other packages depend on a certain package. Show usage This is usage example $ composer depends psr/log symfony/debug v3.2.2 requires psr/log (~1.0)
Unfortunately* Composer doesn’t support Git submodules, as the main aim of Composer is to provide a similar inter-project dependency functionality and it would be pointless to try to replicate submodules in Composer. I have the same problem that you are trying to solve, of developing a library while simultaneously developing the application that uses that … Read more
To quote from the Composer manual “Config” section: sort-packages Defaults to false. If true, the require command keeps packages sorted by name in composer.json when adding a new package. So if you run composer config sort-packages true you command Composer to add the following to your composer.json file: { “config”: { “sort-packages”: true } } … Read more
First, run: composer config –list –global //this will get the composer home path. [home] /root/.composer //it’s my composer home path. And then, edit the config.json, make it like this: { “config”: { “github-protocols”: [ “https” ] }, “repositories”: { “packagist.org”: { “type”: “composer”, “url”: “https://packagist.org” } } } It will make the packagist connection force … Read more
You can ignore packages to be downloaded with the replace property of your composer.json: https://getcomposer.org/doc/04-schema.md#replace That way you tell composer, that you take or took care of that package’s content on your own. This can help you to ignore a package your are sure you do not need, but it is kind of hacky. So … Read more
Purpose of the content hash As you can see in Composer\Package\Locker::getContentHash(), the content hash takes into account the following fields of composer.json: $relevantKeys = array( ‘name’, ‘version’, ‘require’, ‘require-dev’, ‘conflict’, ‘replace’, ‘provide’, ‘minimum-stability’, ‘prefer-stable’, ‘repositories’, ‘extra’, ); The only reason for the content hash to change is a change of one of the values of … Read more
PSR-4 standard requires of you a strict filesystem structure based on namespaces. Say you have an app in src directory with App namespace, then all sub-namespaces will mirror subdirectories and class names will be the same as file names without the .php extension. { “autoload”: { “psr-4”: { “App\\”: “src/” } } } src/ Foo/ … Read more
This is not possible in Composer. However, there are some ways to do it: When you run the update or install command with –prefer-dist, Composer tries to download the archive on github. You can remove the test directory from the archives by putting this in a .gitattributes file in the root directory of your project: … Read more
How to require a specific Git tag? Change the version requirement to dev-master, followed by a hash # and the Git tag name, e.g. v0.5.0, like so: “require”: { “vendor/package”: “dev-master#v0.5.0” } How to require a specific Git commit? Change the version requirement to dev-master, followed by a hash # and the Git commit reference, … Read more