Weave Code
Laravel Php Cs Fixer Laravel Package
stechstudio/laravel-php-cs-fixer
A Laravel wrapper around PHP-CS-Fixer that adds Artisan commands to check and fix your code style with sensible defaults. Configure rules and paths in a single config file, then run fixes locally or in CI for consistent formatting across your project.
Artisan Command for FriendsOfPHP/PHP-CS_Fixer
Frequently asked questions about Laravel Php Cs Fixer
- What is stechstudio/laravel-php-cs-fixer?
- It is a Laravel wrapper around FriendsOfPHP/PHP-CS-Fixer that exposes code style checking and fixing through Artisan commands. It adds sensible defaults and a single config file for rules and paths. It is development tooling only and has no runtime role in a Laravel application.
- How do I install stechstudio/laravel-php-cs-fixer in a Laravel app?
- Install it as a development dependency with composer require --dev stechstudio/laravel-php-cs-fixer. Laravel package discovery should register the service provider automatically. Publish the package config if you need to customize rules or paths, then run the provided Artisan commands.
- Does stechstudio/laravel-php-cs-fixer support Laravel 11 and Laravel 12?
- There is no confirmed support statement in the provided context, and the last release was February 2022. That predates Laravel 11, Laravel 12, PHP 8.3, PHP 8.4, and recent PHP-CS-Fixer majors. Treat compatibility as unproven and run a Composer resolution spike on your exact PHP, Laravel, and PHP-CS-Fixer matrix before adopting.
- How do I configure PHP-CS-Fixer rules and paths with this Laravel package?
- The package is designed to centralize PHP-CS-Fixer rules and target paths in a single config file. You typically publish that config and edit it rather than passing many CLI flags. Keep the rules aligned with your team coding standard so switching tools later does not cause formatting churn.
- What Artisan commands does stechstudio/laravel-php-cs-fixer provide?
- It provides Artisan commands to check code style and to apply fixes. The wrapper is a thin layer over PHP-CS-Fixer, so behavior depends on the underlying fixer version it resolves. Confirm available options such as dry-run, diff, path, config, cache, and parallel execution in your installed version.
- Can I use stechstudio/laravel-php-cs-fixer in CI for a formatting check?
- You can use the check workflow in CI if the command returns a non-zero exit code when style violations are found. Verify dry-run and diff behavior in a non-interactive CI environment before making it a required job. Also confirm that the resolved PHP-CS-Fixer version supports the cache and parallel options your pipeline expects.
- Is stechstudio/laravel-php-cs-fixer maintained and safe to adopt?
- The last release was 2022-02-10, so the project should be treated as stale rather than actively maintained. It has a modest star count and a low overall score in the assessment. Dependency drift is the main concern because a stale wrapper can constrain PHP-CS-Fixer and block PHP or Laravel upgrades.
- How does stechstudio/laravel-php-cs-fixer compare to Laravel Pint?
- Laravel Pint is the first-party formatter built on PHP-CS-Fixer and is usually the better default for Laravel projects. Direct PHP-CS-Fixer invocation is also a clean option if you want full control without an extra wrapper. This package only adds Artisan ergonomics, so choose it only if that command workflow is specifically valuable and compatibility is verified.
- What are the production risks of using stechstudio/laravel-php-cs-fixer?
- It is require-dev tooling, so production runtime and security exposure are limited. The real risks are dependency drift, CI supply-chain consistency, and developer environment mismatch. Pin versions, assign an internal owner, and avoid letting it become a strategic dependency.
- How do I remove stechstudio/laravel-php-cs-fixer or migrate to Pint later?
- Removing it should be straightforward because it is dev-only: drop the package, add Laravel Pint or direct PHP-CS-Fixer, and update Composer scripts and CI jobs. Keep the same rule set during migration to avoid a large formatting diff. Verify that developer workflows and CI exit-code contracts remain unchanged.
Weaver
How can I help you explore Laravel packages today?