Weave Code
Php Cs Fixer Config Laravel Package
irstea/php-cs-fixer-config
A reusable PHP-CS-Fixer configuration package that provides an opinionated, consistent coding style for PHP and Laravel projects. Install it to standardize formatting and linting across repositories, with sensible defaults and easy customization.
Jeux de règles pour php-cs-fixer.
Frequently asked questions about Php Cs Fixer Config
- How do I install irstea/php-cs-fixer-config in a PHP or Laravel project?
- It is a development-only ruleset, so install it with the --dev flag: composer require --dev irstea/php-cs-fixer-config. The repository is hosted on gitlab.irstea.fr rather than Packagist, so you will normally need a VCS repositories entry in composer.json and credentials (SSH key or token) configured for every developer and CI runner. After installing, point your .php-cs-fixer.dist.php config at the provided ruleset.
- Is irstea/php-cs-fixer-config available on Packagist?
- No public Packagist listing is visible for this package. You will need to add a Composer VCS repository entry pointing at https://gitlab.irstea.fr/pole-is/tools/php-cs-fixer-config.git, and access must be granted by the upstream owner. Because that GitLab instance belongs to a third party, availability of the dependency is coupled to their internal infrastructure.
- Is this a runtime dependency or a dev-only dependency?
- It is strictly a development-time dependency. The package ships php-cs-fixer configuration, not a service provider, middleware, or any production autoload footprint, so it should always be installed with require-dev. Nothing from it runs in a deployed Laravel application.
- Which PHP and php-cs-fixer versions does this ruleset support?
- Version constraints are not documented in the overview, so verify the composer.json of the branch or commit you intend to use before adopting it. Confirm the package is compatible with the php-cs-fixer major version your toolchain resolves, since fixer APIs change between majors. Test against your full supported PHP matrix before running it on any codebase.
- Does this package conflict with Laravel Pint?
- Pint wraps php-cs-fixer, so running both means two style authorities in the same repository. That produces divergent formatting, confusing CI failures, and duplicated ownership of the ruleset. Pick one as the house style authority rather than layering them; the package is framework-agnostic and works fine without Pint.
- Can I customize or override the rules in the ruleset?
- Yes. Because it is plain php-cs-fixer configuration, you merge or override the rule array in your own .php-cs-fixer.dist.php and add project-specific paths or excludes. Treat the upstream rules as a baseline and keep your overrides in your own repository so upgrades stay predictable.
- What license is irstea/php-cs-fixer-config released under, and can I fork it?
- The license is not stated in the available information, and an internal institute tool may well be all-rights-reserved. That matters because a restrictive license can block redistribution and even internal reuse. Ask the upstream owner before adopting, and if forking is not permitted, transcribe the rule array into your own config file instead.
- How do I run this ruleset in CI to enforce coding style?
- Run php-cs-fixer with --dry-run --diff in CI so the job fails when files are not formatted. Roll it out as advisory first on a single service, then make it blocking once the churn is understood. Ensure the CI runner has credentials for the GitLab host if you install the ruleset directly from the VCS repository.
- Does the package ship custom fixers or only configuration?
- It is described as a set of rules for php-cs-fixer, which usually means configuration only, but this has not been confirmed. If custom fixers are included, they must be autoloadable in the tooling context and the blast radius of adoption grows. Check the repository contents before running it against production code.
- Are there release tags, and how should I pin the version?
- No tags are visible, so pinning probably means a specific commit SHA on a branch such as dev-main rather than a semantic version constraint. The safer approach is to fork or mirror the repository into your own GitLab and consume the pinned SHA from there. That converts an external availability dependency into an internal one and makes upgrades a deliberate quarterly diff against upstream.
Weaver
How can I help you explore Laravel packages today?