- How do I install wucdbm/php-cs-fixers in a Laravel project?
- Install it as a dev dependency with composer require --dev wucdbm/php-cs-fixers, since it only provides PHP-CS-Fixer rules and has no runtime footprint. Then register its custom fixers in your .php-cs-fixer.dist.php or .php-cs-fixer.php config and enable the rule set you want. Keep it out of production builds by using composer install --no-dev.
- Is wucdbm/php-cs-fixers compatible with Laravel 10 or 11?
- Probably not without changes: the last release was June 2020, which places it in the PHP-CS-Fixer 2.x era, and PHP-CS-Fixer 2.x does not support PHP 8. Laravel 10 and 11 require PHP 8.1+, so Composer may refuse to install it on those stacks. Verify with composer why-not in a throwaway branch before adopting it.
- Does wucdbm/php-cs-fixers work with Laravel Pint?
- Likely not in the same Composer install. Pint pins its own PHP-CS-Fixer 3.x, while this package appears to target PHP-CS-Fixer 2.x custom fixers, and the fixer contract changed between those major versions. For most Laravel teams the practical choice is to port the ruleset into Pint rather than add this package.
- What PHP-CS-Fixer version does wucdbm/php-cs-fixers require?
- The package's last release date of June 2020 strongly suggests it targets PHP-CS-Fixer 2.x, but you should confirm the exact friendsofphp/php-cs-fixer constraint in its composer.json. That matters because custom fixers implement FixerInterface, and 3.x replaced getName() with getDefinition(). If the constraint is ^2.x, its fixers will not load against current PHP-CS-Fixer without a rewrite.
- How do I register custom fixers from wucdbm/php-cs-fixers?
- In your .php-cs-fixer.dist.php config, use registerCustomFixers() with the package's fixer classes, then reference the rules by name in your rules array. The package is designed to plug into existing PHP-CS-Fixer configurations rather than replace them. Test on a small directory first to avoid a repo-wide reformat.
- Can I use wucdbm/php-cs-fixers in CI?
- Yes in principle: it is dev-only tooling meant for CI lint jobs and local pre-commit checks. The caveat is the PHP version in your CI image; if the package requires PHP-CS-Fixer 2.x, it will not run on a PHP 8.1+ pipeline. Pin the CI tool image independently from application runtime if you need to evaluate or port the rules.
- Is wucdbm/php-cs-fixers still maintained?
- The evidence says no: three stars, zero dependents, one maintainer, and no releases in roughly five years. It is small, MIT-licensed, and auditable, so supply-chain risk is low, but you should assume you are the de facto maintainer if you adopt it. For a long-lived Laravel project, porting the rules into Pint or an internal dev-tools package is usually safer.
- What are alternatives to wucdbm/php-cs-fixers for Laravel?
- Laravel Pint is the first-party default and covers most PSR-12 and Laravel style needs with a maintained PHP-CS-Fixer 3.x underneath. Stock PHP-CS-Fixer with a custom .php-cs-fixer.dist.php also works if you want explicit rule control. If the package's rule set has value, translate it into pint.json or an internal fixer package instead of depending on an abandoned one.
- Does wucdbm/php-cs-fixers require a service provider or config publishing?
- No. It is static-analysis tooling, not a Laravel package with runtime integration, so there is no service provider, container binding, config publishing, database, queue, or HTTP surface. Integration happens entirely in your PHP-CS-Fixer config file and Composer's require-dev section.
- Should wucdbm/php-cs-fixers be in require or require-dev?
- Always require-dev. It only supplies PHP-CS-Fixer custom fixers and rule sets, and has zero runtime footprint in a Laravel application. Keeping it out of require means production builds with composer install --no-dev will not carry it.