- What is blastcloud/chassis?
- BlastCloud Chassis is a Composer package for Laravel that provides a framework and conventions for building declarative testing libraries for PHP and HTTP request packages. Its overview also describes it as a reusable application foundation and scaffolding package for bootstrapping maintainable Laravel projects. Check the package README and composer.json for the exact features included in your version.
- How do I install blastcloud/chassis?
- Install it with Composer using composer require blastcloud/chassis. Because the README excerpt is not available here, follow the package documentation for any Laravel service provider registration, configuration publishing, or test setup steps. Confirm whether it belongs in require or require-dev based on whether you use it only for testing libraries or also as application scaffolding.
- Which Laravel versions does blastcloud/chassis support?
- The provided context does not list supported Laravel or PHP versions. Check the package composer.json for require constraints and review the README or release notes before adding it to an existing application. This is especially important if you are evaluating it for an older Laravel project.
- What is a declarative testing library in this context?
- A declarative testing library lets developers describe expected HTTP requests, responses, or testing scenarios in a structured way instead of writing every assertion procedurally. Chassis provides a framework and conventions for building that kind of testing library for PHP or HTTP request packages. It is aimed at package authors and teams creating reusable test tooling, not just at writing one-off application tests.
- Can I use blastcloud/chassis with PHPUnit or Pest?
- The context does not explicitly confirm PHPUnit or Pest integration. Since Chassis is described as a framework for building declarative testing libraries for PHP, it is likely intended to sit alongside a PHP test runner, but you should verify the supported runners in the README or composer.json. Check for existing examples before standardizing your test suite around it.
- Does blastcloud/chassis replace Laravel's built-in testing tools?
- No, it should be treated as a foundation for building declarative testing libraries rather than a direct replacement for Laravel's HTTP testing helpers, PHPUnit, or Pest. Laravel's built-in tools remain the baseline for application tests, while Chassis is aimed at creating reusable testing conventions and scaffolding. Review the package documentation to see how it complements your existing test stack.
- Should blastcloud/chassis be installed in production?
- If you use Chassis only to build or run declarative testing libraries, keep it in require-dev and do not load it in production. If you use its application foundation or scaffolding features, review the package documentation and dependency constraints before deploying. Always confirm that any service providers or configuration files are safe for your production environment.
- Is blastcloud/chassis actively maintained?
- The provided context does not include repository details, release history, or TPM assessment data, so maintenance status cannot be confirmed from this information alone. Check Packagist, the GitHub repository, open issues, and recent releases before adopting it. For long-lived projects, also review whether the package supports your current Laravel and PHP versions.
- What are alternatives to blastcloud/chassis?
- Alternatives depend on whether you need a declarative testing-library framework or Laravel application scaffolding. For HTTP testing, developers commonly use Laravel's built-in HTTP testing helpers, PHPUnit, Pest, and package-specific fakes or test helpers. Chassis is distinctive in its focus on providing a reusable foundation for building declarative testing libraries for PHP and HTTP request packages.
- How do I configure blastcloud/chassis in a Laravel project?
- The provided README excerpt does not include configuration instructions. Start by checking the package README for service provider registration, publishable config files, environment variables, and test bootstrap requirements. Then inspect composer.json and any config directory in the package to confirm what is optional versus required for your use case.