Weave Code
Laravel Coding Standards Laravel Package
jumptwentyfour/laravel-coding-standards
A package of opinionated coding standards for Laravel projects, bundling ready-made configs and rules so teams can enforce consistent PHP style and static analysis with minimal setup. Install it to keep new and existing apps aligned on the same conventions.
Jump24 coding standards for Laravel based projects.
Frequently asked questions about Laravel Coding Standards
- How do I install jumptwentyfour/laravel-coding-standards in a Laravel project?
- Install it with Composer as a development dependency, for example composer require --dev jumptwentyfour/laravel-coding-standards. Then follow the repository README for any publish or config steps, because the package may expose config files you need to copy into your project. Commit the resulting configuration so every team member and CI run uses the same rules.
- Which Laravel and PHP versions are supported?
- The exact Laravel and PHP version constraints are declared in the package's composer.json, so check those before installing. Because the package targets Laravel-based projects, it is best suited to apps on currently supported Laravel releases. If you maintain older applications, verify compatibility or pin a package version that matches your stack.
- What coding standards and static analysis tools does this package configure?
- The package is described as bundling opinionated configs and rules for PHP style and static analysis in Laravel projects. The exact underlying tools, rule sets, and file names are documented in the repository README and configuration files. Review those files before adopting it so you know which checks will run in your pipeline.
- Can I use these coding standards in an existing Laravel application?
- Yes, but running a new rule set across an existing codebase can surface many violations at once. Adopt it incrementally by starting with a baseline, excluding generated or legacy paths, or applying the rules only to changed files first. This keeps the rollout manageable while still aligning new code with the shared conventions.
- How do I customize or override the bundled rules?
- Customization usually means publishing the package configs into your project and editing the rule lists or paths there. Check the README for publish tags and supported override mechanisms, then keep project-specific changes in your own config files. Avoid editing vendor files directly, because those changes are lost on the next Composer update.
- How do I run the coding standards in CI?
- Add the package's commands to your CI pipeline, either directly or through Composer scripts defined in composer.json. Run the style and static analysis checks on every pull request and fail the build when violations are found. Caching dependency installs and analysis results can keep CI times reasonable as the codebase grows.
- Does this package replace Laravel Pint or PHPStan?
- It is best thought of as a shared baseline of opinionated configs and rules rather than a drop-in replacement for the underlying tools. Depending on the release, it may configure or complement tools such as style fixers and static analyzers, but the README is the source of truth. Use it alongside your existing Laravel tooling and adjust overrides where your team needs different behavior.
- Should I require this package in production?
- No, coding standards and static analysis are development-time concerns, so the package should normally be installed with --dev. It does not need to be loaded by your Laravel application at runtime and should not affect production behavior. Keep it out of production deployments unless your build process explicitly needs it.
- How do I handle existing violations in legacy code?
- Start by generating a baseline if the underlying static analysis tool supports one, or exclude legacy directories in the package config. You can also run the checks only on changed files in pull requests and tighten coverage over time. The goal is to stop new violations first, then clean up older code in planned batches.
- What are alternatives to jumptwentyfour/laravel-coding-standards?
- Common alternatives include Laravel Pint for style, PHPStan or Larastan for static analysis, and PHP-CS-Fixer for finer-grained formatting rules. Some teams also maintain their own shared config package so standards can be reused across repositories. This package is most useful when you want Jump24's opinionated baseline without assembling and maintaining those rules yourself.
Weaver
How can I help you explore Laravel packages today?