Download the PHP package mlocati/composer-patcher without Composer
On this page you can find all versions of the php package mlocati/composer-patcher. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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-patcher
composer-patcher
Simple patches plugin for Composer. Applies a patch from a local or remote file to any package required with Composer.
Usage
Example composer.json:
If you use the patches-file configuration key, it must be a local or remote JSON file with this syntax:
Allowing patches to be applied from dependencies
You can use the allow-subpatches to let dependency packages install patches.
It can be:
false[the default] to prevent dependency packages from installing patchestrueto allow all dependency packages installing patches- an array of package handles to whitelist the packages that can install patches
Using patches from HTTP URLs
Composer blocks you from downloading anything from HTTP URLs, you can disable this for your project by adding a secure-http setting in the config section of your composer.json. Note that the config section should be under the root of your composer.json.
However, it's always advised to setup HTTPS to prevent MITM code injection.
Patch levels
In order to specify the level of a patch, you can use the extended form of the patch path.
For example, if the patch level for a patch should be -p4, you can replace
with
It can be:
false[the default] to prevent dependency packages from installing patchestrueto allow all dependency packages installing patches- an array of package handles to whitelist the packages that can install patches
Target packages
You can specify the package versions a patch should be applied to. To do so, simply specify the version in the package handle:
You can use the Composer syntax to specify the applicable version(s).
Patches containing modifications to composer.json files
Because patching occurs after Composer calculates dependencies and installs packages, changes to an underlying dependency's composer.json file introduced in a patch will have no effect on installed packages.
If you need to modify a dependency's composer.json or its underlying dependencies, you cannot use this plugin. Instead, you must do one of the following:
- Work to get the underlying issue resolved in the upstream package.
- Fork the package and specify your fork as the package repository in your root
composer.json - Specify compatible package version requirements in your root
composer.json
Error handling
You can use the extra.patch-errors-as-warnings configuration option to instruct composer-patcher what to do in case of errors.
It can be:
true[the default] to simply output an error message in case of errorsfalseto exit composer in case of errors
Credits
A ton of this code is adapted or taken straight from cweagans/composer-patcher.
Do you really want to say thank you?
You can offer me a monthly coffee or a one-time coffee :wink:
All versions of composer-patcher with dependencies
php Version >= 5.3.2