Weave Code
Php Cs Fixer Config Laravel Package
lin3s/php-cs-fixer-config
A shared PHP-CS-Fixer configuration from Lin3s that standardizes coding style across PHP projects. Install via Composer and extend the predefined rule set to enforce consistent formatting, imports, and conventions with minimal setup in any codebase.
PHP linting tool using PHP CS Fixer for LIN3S projects
Frequently asked questions about Php Cs Fixer Config
- How do I install lin3s/php-cs-fixer-config?
- Install it with composer require --dev lin3s/php-cs-fixer-config, then create a .php-cs-fixer.dist.php file in your project root that returns the package's shipped Config object. Because it is a dev-only tooling dependency it never ships to production and does not affect runtime code. Add the .php-cs-fixer.cache file to .gitignore so the local cache is not committed.
- Does this package work with Laravel projects?
- Yes. The package is framework-agnostic, so it applies to Laravel applications, plain PHP libraries, and monorepos alike. You add it as a require-dev dependency and point your .php-cs-fixer.dist.php at the shared config, then run php-cs-fixer fix locally or in CI. Note that it does not encode Laravel-specific style; if you want Laravel conventions, Laravel Pint is the more direct fit.
- Which PHP CS Fixer version does this package require?
- The last tagged release dates to November 2017, which predates PHP CS Fixer 3.x and its rule renames and Config API changes. That strongly suggests it targets PHP CS Fixer 2.x, so you would need to pin friendsofphp/php-cs-fixer to a compatible 2.x release. Verify the exact constraint in the package's composer.json before adopting, and expect breakage on 3.x.
- Does it support PHP 8.1, 8.2 and 8.3?
- There is no published evidence it has been tested on PHP 8.1, 8.2, or 8.3, and the project has had no releases since 2017 and no dependents. PHP CS Fixer 3.x requires modern PHP versions, and the package's own constraint likely blocks that upgrade. Treat PHP 8.x compatibility as unproven until you try it in a scratch project.
- How do I extend or override the LIN3S ruleset?
- The package exposes a PhpCsFixer\Config object, so you can require it and then call setRules() with your own array, or merge your overrides on top of the shipped rules. That keeps LIN3S conventions as a baseline while letting you disable rules that conflict with your codebase. If you need heavy customization, copying the rules array into a first-party config gives you the same result without the dependency.
- Is lin3s/php-cs-fixer-config still maintained?
- No. It has zero stars, zero dependents, and no tagged release since November 2017, which are strong signals of abandonment. The code is MIT-licensed and small, so you can read and reuse the ruleset, but any incompatibility you hit is yours to fix. Plan for a fork or an in-house replacement rather than upstream support.
- How do I run this config in a CI pipeline?
- Add a CI step that runs vendor/bin/php-cs-fixer fix --dry-run --diff against your source directories so the build fails on style violations. Because the config package is a dev dependency, it installs in CI without touching production artifacts. Cache the Composer downloads and the PHP CS Fixer cache directory to keep the job fast.
- What are the alternatives to this configuration package?
- The most direct alternatives are PHP CS Fixer's built-in @PSR12 and @PhpCsFixer rule sets, Laravel Pint for Laravel-first projects, and a first-party coding-standards package inside your organisation. Each gives you a maintained baseline without depending on an unmaintained config. LIN3S's value is its specific opinionated overrides, which are short enough to copy.
- Can I use this config with Laravel Pint?
- Pint wraps PHP CS Fixer but uses its own preset system configured through pint.json, so it cannot consume this package's Config object directly. You can reproduce the same conventions by translating the LIN3S rules into a Pint preset or a custom rules block. For new Laravel projects, Pint is usually the lower-friction choice.
- Should I install the package or copy the rules into my own config?
- For most teams, harvesting the ruleset is the better trade: copy the rule array out of the repository, translate any PHP CS Fixer 2.x rule names to their 3.x equivalents, and keep it in your own standards package. That captures the formatting opinions with none of the abandonment risk. Only install the package verbatim if you can pin PHP CS Fixer 2.x and accept an unsupported linter.
Weaver
How can I help you explore Laravel packages today?