- Can I install mkoprek/request-validation-bundle in a Laravel application?
- No. It is a Symfony bundle and depends on the Symfony kernel, dependency-injection compiler passes, and bundle registration, none of which exist in Laravel. There is no service provider, facade, or publishable config, so the only reusable part is the validation logic itself. The practical path is to port those rules into Laravel Form Requests or Validator rules.
- Is this package a Laravel package or a Symfony bundle?
- It is a Symfony bundle, published under a Symfony-oriented vendor namespace, despite being framed as a Laravel/PHP package in some intake forms. The assessment found no Laravel service provider, facade, config file, or framework-agnostic core. Symfony bundles are not portable to Laravel because Laravel has no bundle registration or compiler-pass extension point.
- How do I install and configure request-validation-bundle?
- In a Symfony application you would require it via Composer, register the bundle in bundles.php, and configure it through the bundle's Configuration tree or services.yaml. There is no documented Laravel installation path and no publishable config. Before attempting either, check the composer.json constraints for PHP and Symfony components, because they are unverified.
- Does it support Laravel 10 or Laravel 11?
- There is no evidence of a Laravel constraint, service provider, or facade, so nothing indicates support for Laravel 10, 11, or any other version. Composer resolution in a current Laravel app is likely to fail or, at best, install code that is never wired up. Treat Laravel support as absent rather than pending.
- What PHP and Symfony versions does request-validation-bundle support?
- Unverified. The package declares no Laravel constraint, and its PHP and Symfony component constraints need to be read directly from composer.json. The last release was 2023-05-24, which predates meaningful PHP 8.3 and 8.4 adoption and the Symfony 6.4 to 7.x transition. Assume adverse compatibility until you test it yourself.
- Is mkoprek/request-validation-bundle maintained and safe for production?
- Treat it as unmaintained. It has zero stars, zero dependents, a single maintainer, and no release since 2023-05-24, so there is no field validation, no downstream bug reports, and little pressure to ship compatibility patches. The MIT license removes legal friction and permits a fork, but a fork means you inherit maintenance permanently. It is not recommended for production adoption in a Laravel stack.
- What is the best alternative for request validation in Laravel?
- Laravel's built-in Validator, Form Requests, and rule objects are the direct alternative and are already maintained, documented, and familiar to most teams. They cover the same centralization goal: move incoming request checks out of controllers into reusable, testable classes. Porting this bundle's rule set into Form Requests gives you the same consistency without a new dependency or fork.
- How do I migrate this bundle's rule sets to Laravel validation?
- Extract the validation constraints from the bundle and re-express them as Laravel Validator rules or Form Requests, then map failures to Laravel's standard 422 JSON or redirect responses. This is bounded effort, produces idiomatic code, and creates no ongoing maintenance obligation. Only consider a fork-and-wrap adapter if the package encodes genuinely non-obvious domain logic that you cannot restate cleanly.
- Does request-validation-bundle have a test suite, and does it run on current PHP?
- Unknown. The evaluation found no evidence of a test suite, so there is no proof the code runs on current PHP 8.3 or 8.4. Ask the maintainer directly or run the suite locally inside a Symfony 6.4 or 7.x app before relying on any behavior. Without tests, porting its rules is guesswork.
- Should I fork request-validation-bundle to add Laravel support?
- Forking is possible under MIT but costly: you would wrap the underlying validator in a Laravel ServiceProvider, publish config, and map exceptions to Laravel's validation response format. That creates a permanent hybrid fork that new engineers will not recognize, and the effort likely exceeds writing the same rules natively. Fork only if the rule set is uniquely valuable and you accept long-term maintenance.