Download the PHP package iwink/composer-global-installer without Composer
On this page you can find all versions of the php package iwink/composer-global-installer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download iwink/composer-global-installer
More information about iwink/composer-global-installer
Files in iwink/composer-global-installer
Package composer-global-installer
Short Description Plugin to install Composer dependencies in a global directory.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package composer-global-installer
Composer global installer
A plugin to install stable, remote Composer packages in a global
vendor directory. The path to a global installed package is
[global-vendor-dir]/[pretty-package-name]/[pretty-package-version]; for example, symfony/console:v5.3.1 might be
found under /usr/local/lib/composer/vendor/symfony/console/v5.3.1. It creates symlinks in the local vendor directory
(/path/to/project/vendor) to assist IDEs. The
autoloader will point to the resolved global vendor/package directory. You should make sure the global vendor directory
is writable.
Installation
To install this package, run composer require iwink/composer-global-installer. It's also possible to install the
plugin global: composer global require iwink/composer-global-installer.
Options
You can configure the plugin using the extra.global-installer key in composer.json (and in the global
$COMPOSER_HOME/composer.json):
path: Path to global vendor directory. (default:/usr/local/lib/composer/vendor/)exclude: Array of excluded package names (including vendor prefix), these packages will be installed locally.exclude-bin: Whether to exclude any packages that hold a binary. (default:false)stabilities: Array of supported branch stabilities. (default:["alpha", "beta", "RC", "stable"])
Example:
To disable the entire plugin, you can pass false to the extra.global-installer key:
Caveats
Unsupported libraries
Some libraries, like
laminas/laminas-zendframework-bridge and
phpunit/phpunit, expect the package to be installed locally. If one
or more of your projects depend on such libraries, you can exclude them in the global composer configuration:
composer global config --json extra.global-installer.exclude '["laminas/laminas-zendframework-bridge", "phpunit/phpunit"]'
Packages with patches
If you use a seperate plugin (for example cweagans/composer-patches)
to apply patches to packages, it might not be a good idea to install those packages globally.
Other projects which use the same package will receive the changes from the applied patch as well.
To prevent this, we recommend excluding packages which you have patched.
All versions of composer-global-installer with dependencies
composer-plugin-api Version ^2.1