composer-patches
Simple patches plugin for Composer (by cweagans)
laravel-strict-coding-standard
PHP_CodeSniffer rules for Laravel to force the "right" design of the app (by vladyslavstartsev)
| composer-patches | laravel-strict-coding-standard | |
|---|---|---|
| 10 | 1 | |
| 1,475 | 45 | |
| - | - | |
| 7.6 | 1.9 | |
| 8 days ago | about 1 year ago | |
| PHP | PHP | |
| BSD 3-clause "New" or "Revised" License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
composer-patches
Posts with mentions or reviews of composer-patches.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-28.
-
Mechanics of (and ethics of) upgrading a PHP Joomla plugin
if you're using composer with joomla, and the plugin is installed via composer, you can commission someone to make the necessary changes, create a git diff patch that encapsulates the changes, then leverage cweagans/composer-patches to make it work. if/when new changes are necessary, they can build a new patch.
-
Laravel considered harmful
I've had problems with libraries using final having an API that isn't customizable enough in a particular way I need because I'm innovating in some way they could never have considered in the past, so my choice ends up either needing to fork the library or monkey patch it with https://github.com/cweagans/composer-patches so I can get rid of final so I can keep using it. They wouldn't accept a change in API or behaviour because it would break things for other users, etc.
-
Thoughts on running patches in production?
There are cool tools to integrate patches from drupal.org (or your own custom patches) into your composer managed drupal website. For example (not drupal specific but works well with drupal+composer): https://github.com/cweagans/composer-patches
-
Is there a way to apply a patch to an AUR package on the fly, without editing the PKGBUILD?
If the PR get's merged, I want `yay` or `pacman` to skip the patch. Ideally it would be declared in a pacman.patches file or similar to what https://github.com/cweagans/composer-patches provides for composer PHP package managment.
-
PSA for macOS users with composer workflows.
This has been an issue for a while, and is outlined here: - https://github.com/cweagans/composer-patches/issues/172#issuecomment-587147692 - https://github.com/cweagans/composer-patches/issues/326
-
Installing patches in Drupal 8
Install a package that allows the composer to work with patches:
- Procedure for critical dependency lagging behind?
-
Best way to handle a bug in a composer package?
And if for some reason you do not want to make a fork, you can also create a composer patch with the help of https://github.com/cweagans/composer-patches
-
Modifying a Package Controller
https://github.com/cweagans/composer-patches - this lets you patch packages when they are pulled in by Composer. I have used it in the past to get minor bugfixes into a project ASAP without having to wait for upstream or forking the entire package.
- troubles with dd or What are best practices for patching Symphony?
laravel-strict-coding-standard
Posts with mentions or reviews of laravel-strict-coding-standard.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-28.
-
Laravel considered harmful
You can even do it automatically; LaravelStrictCodingStandard.Laravel.DisallowUseOfFacades in PHP_CodeSniffer. https://github.com/vladyslavstartsev/laravel-strict-coding-standard
What are some alternatives?
When comparing composer-patches and laravel-strict-coding-standard you can also consider the following projects:
Repman - Repman - PHP Repository Manager: packagist proxy and host for private packages
Slim - Slim Framework 4 Skeleton Application
Packagist - Package Repository Website - try https://packagist.com if you need your own -
Torch - Examples of using each Illuminate component in non-Laravel applications
comments - Native comments for your Laravel application.
ideas - Issues board used for Laravel internals discussions.
ComposerRequireChecker - A CLI tool to check whether a specific composer package uses imported symbols that aren't part of its direct composer dependencies
bypass-finals - Removes `final` and `readonly` keywords from source code on-the-fly and allows mocking of final methods and classes. It can be used together with any test tool such as PHPUnit or Mockery.
WordPress Packagist - WordPress Packagist — manage your plugins with Composer
Laravel - The Laravel Framework.
composer-diff - Compares composer.lock changes and generates Markdown report so you can use it in PR description.
Sylius - Open Source eCommerce Framework on Symfony
composer-patches vs Repman
laravel-strict-coding-standard vs Slim
composer-patches vs Packagist
laravel-strict-coding-standard vs Torch
composer-patches vs comments
laravel-strict-coding-standard vs ideas
composer-patches vs ComposerRequireChecker
laravel-strict-coding-standard vs bypass-finals
composer-patches vs WordPress Packagist
laravel-strict-coding-standard vs Laravel
composer-patches vs composer-diff
laravel-strict-coding-standard vs Sylius