- How do I install matt-allan/laravel-code-style in a Laravel project?
- Install it as a Composer dev dependency with composer require --dev matt-allan/laravel-code-style. Because it is development tooling, it should stay in require-dev and never be added to production runtime dependencies. After installation, publish or commit its configuration and expose a Composer script or CI job to run the formatter in check mode on pull requests.
- Does matt-allan/laravel-code-style work with the latest Laravel versions?
- Probably not reliably, because the repository is archived and its PHP, Laravel, and php-cs-fixer constraints may not resolve against current versions. Before adopting it, run a compatibility spike in a disposable branch using composer why-not against your target stack. If Composer resolution fails, the package is not viable without a fork.
- What is the difference between laravel-code-style and Laravel Pint?
- Laravel-code-style is a legacy wrapper around PHP-CS-Fixer that applies Laravel-specific rules and presets, while Laravel Pint is the first-party, Laravel-maintained formatter. Pint is already the default expectation in current Laravel projects and is the recommended standard for new work. Laravel-code-style is best treated as legacy convenience tooling rather than a strategic dependency.
- Should I use matt-allan/laravel-code-style in production?
- No. It is a development-time code formatter and should sit in require-dev with no production deployment footprint. Running it in production would add unnecessary supply-chain and CI risk without providing runtime value. Keep it limited to local development and CI formatting checks.
- How do I run laravel-code-style in CI to check formatting?
- Expose the formatter through a Composer script or CI job, then run it in check mode on pull requests so formatting drift fails the build. Pin the package version and commit the generated configuration to keep output stable. Because underlying PHP-CS-Fixer versions can change formatting results, expect occasional noisy diffs or CI failures after dependency updates.
- Can I customize the code style rules used by laravel-code-style?
- Yes, it wraps PHP-CS-Fixer, so you can customize rules through its configuration and presets. For migration planning, document any custom formatting rules and determine whether they can be expressed in Laravel Pint or a maintained PHP-CS-Fixer config. Preserving package-specific rules is one of the key questions to resolve before moving to Pint.
- Why is matt-allan/laravel-code-style archived and is it still maintained?
- The repository is archived, which means there is no upstream compatibility work, no bug-fix cadence, and no security-response process. It has effectively been superseded by Laravel Pint as the supported Laravel standard. Existing users should pin the version, constrain it to dev and CI use, and plan a migration to Pint.
- How do I migrate from laravel-code-style to Laravel Pint?
- First freeze current behavior by pinning the package version, committing the generated config, and running the formatter in CI check mode. Then pilot Pint in a branch using the same or nearest-equivalent ruleset, compare diffs, and resolve intentional differences. Once Pint is accepted, replace the package command in Composer scripts and CI, remove the archived dependency, and update developer documentation.
- Does laravel-code-style support PHP 8 and newer PHP-CS-Fixer versions?
- Support is uncertain because the package is archived and its dependency constraints may not resolve against newer PHP or PHP-CS-Fixer releases. Validate with a compatibility matrix covering supported PHP versions, Laravel versions, and the resolved php-cs-fixer version. Test in a clean CI image and confirm the command or binary is available after install.
- What are alternatives to matt-allan/laravel-code-style for Laravel formatting?
- Laravel Pint is the primary alternative and the recommended standard for new Laravel projects. A maintained PHP-CS-Fixer configuration is another option if you need specific rules that Pint does not cover. For greenfield applications or platform teams standardizing on current Laravel, skip laravel-code-style and evaluate Pint directly.