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
During the installation you got a message Composer successfully installed to: … this indicates where Composer was installed. But you might also search for the file composer.phar on your system. Then simply: Delete the file composer.phar. Delete the Cache Folder: Linux: /home/<user>/.composer Windows: C:\Users\<username>\AppData\Roaming\Composer That’s it.
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
I encountered this using it in Mac, resolved it by using –ignore-platform-reqs option. composer install –ignore-platform-reqs After installing with this method, if the package that defines the requirement attempts to use any functions from the specified PHP extension, it will fail irrevocably.
I started getting a similar error and the reason was that Github recently changed the format of their auth tokens: https://github.blog/changelog/2021-03-31-authentication-token-format-updates-are-generally-available/ To resolve the error: Find the composer/auth.json file (if you’re running the project in a container, you’ll have to bash into it and find the file in there) Remove its github.com entry. Your file … Read more
You can autoload specific files by editing your composer.json file like this: “autoload”: { “files”: [“src/helpers.php”] } (thanks Kint)
Different Environments Typically, software will run in different environments: development testing staging production Different Dependencies in Different Environments The dependencies which are declared in the require section of composer.json are typically dependencies which are required for running an application or a package in staging production environments, whereas the dependencies declared in the require-dev section are … 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 run composer show -i (short for –installed). In the latest version just use composer show. The -i options has been deprecated. You can also use the global instalation of composer: composer global show
The “Can only install one [x, y]” message appears when two different packages point to the same dependency, but different major, mutually exclusive versions where only one can be installed. Troubleshooting For example, one version can be “locked at” due to the information present in your composer.lock file which may conflict with what you’re trying … Read more