cweagans/composer-patches
Apply and manage patch files to Composer dependencies. Lets you keep fixes and tweaks outside vendor/ while still using normal Composer updates, with support for multiple patches per package, remote patch URLs, descriptions, and CI-friendly installs.
{{< lead text="Common problems that people have run into and how to fix them." >}}
If you've encountered a problem, a good first step is to run [composer patches-doctor]({{< relref "../usage/commands.md#composer-patches-doctor" >}}). This will run a few checks against your system and look for common configuration errors.
If a command is failing and composer patches-doctor doesn't give you any errors, you should re-run your command with extra verbose output. Example: composer -v install. Composer Patches will usually display extra information about why something is failing in any of the verbose output modes. Composer Patches only emits extra output in the normal verbose mode (composer -v), but if you're having other problems with Composer, you can also add one or two additional v's to your command (composer -vv or composer -vvv) to get extra information from Composer itself.
See the [system requirements]({{< relref "../getting-started/system-requirements.md" >}}) page for the minimum supported versions of PHP, Composer, and other software. Upgrade your software using the method appropriate for your operating system.
Composer Patches requires git to be installed in order to apply patches. Previous versions of the plugin relied on
various versions of patch, but that is no longer the case. Make sure you have git installed and you should be all set.
If you've been referred here, you're trying to download patches over HTTP without explicitly telling Composer that you want to do that. See the [secure-http]({{< relref "../usage/configuration.md#secure-http" >}}) documentation for more information.
How can I help you explore Laravel packages today?