Weave Code
Dev Tools Laravel Package
soyhuce/dev-tools
Soyhuce Dev Tools bundles opinionated development tooling for Laravel and PHP projects, standardizing code quality, static analysis, formatting, and testing through shared configurations and sensible defaults. It simplifies maintaining a consistent developer workflow across apps and packages.
Propose a lot of tools for laravel development
Frequently asked questions about Dev Tools
- What is soyhuce/dev-tools used for?
- Soyhuce Dev Tools bundles opinionated development tooling for Laravel and PHP projects. It standardizes code quality, static analysis, formatting, and testing through shared configurations and sensible defaults. It is intended for development and CI workflows rather than production runtime use.
- How do I install soyhuce/dev-tools in a Laravel project?
- Install it as a Composer dev dependency, for example with composer require --dev soyhuce/dev-tools, and make sure your project's PHP and Laravel constraints match the package's composer.json requirements. Then wire its shared configurations into your local scripts and CI pipeline. Because it is development tooling, it should stay in require-dev rather than production dependencies.
- Does soyhuce/dev-tools support Laravel 12?
- Version 4.1.0 adds Laravel 12 to the package's test matrix, which improves confidence that the tooling is exercised against Laravel 12. CI coverage is not the same as a formal compatibility guarantee, so validate the package in a branch against your application. Also check the package's PHP and Laravel constraints before upgrading.
- Is soyhuce/dev-tools a production dependency?
- No, it is best treated as a development and CI tooling dependency. Keep it in require-dev and confirm after updates that no production dependency was introduced. Its purpose is to standardize developer workflow and quality checks, not to affect production code paths.
- What changed in soyhuce/dev-tools version 4.1.0?
- Version 4.1.0 is a narrow maintenance release that adds Laravel 12 to the package's test matrix. The release notes do not indicate new features, breaking changes, deprecations, or public API changes. Treat it as a routine minor upgrade but still validate it in a branch.
- How do I upgrade soyhuce/dev-tools from 4.0.0 to 4.1.0?
- Pin 4.1.0 in require-dev on a branch, update only this package, and inspect the lockfile diff. Run your application test suite and CI matrix, including static analysis and code-style checks, then confirm no production dependency was introduced. This keeps the upgrade routine while catching any dev-dependency or tooling conflicts.
- Which PHP and Laravel versions does soyhuce/dev-tools support?
- The provided release notes only confirm that Laravel 12 was added to the package's test matrix; they do not enumerate the full supported PHP and Laravel range. Check the package's composer.json constraints for the authoritative PHP and framework requirements. Validate those constraints against your application before adopting 4.1.0.
- Can soyhuce/dev-tools conflict with other Composer dev dependencies?
- Transitive dev-dependency conflicts are possible, especially around PHPUnit or Pest, static analysis tools, and code-style tooling. Validate upgrades on a branch and inspect the Composer lockfile diff before merging. Keeping tool versions aligned across repositories reduces the chance of version drift and CI failures.
- Is soyhuce/dev-tools suitable for standardizing CI across multiple Laravel services?
- Yes, its shared configurations and sensible defaults can help standardize code quality, formatting, static analysis, and testing across Laravel services and packages. The tradeoff is a small CI runtime cost for the added compatibility signal. Assign ownership for version bumps and CI matrix maintenance to avoid drift across repositories.
- How should teams test a soyhuce/dev-tools upgrade?
- Run the application test suite and full CI matrix after updating the package in a branch. Include static analysis and code-style checks, and compare the Composer lockfile to confirm only expected dev dependencies changed. Remember that package-level Laravel 12 tests do not replace application-level compatibility testing.
Weaver
How can I help you explore Laravel packages today?