- Is requestum/api-bundle compatible with Laravel?
- No, requestum/api-bundle is a Symfony bundle, not a Laravel package. Its naming, kernel registration, and dependency injection extension are Symfony-specific, and there is no Laravel service provider. Laravel teams should treat it as a design reference rather than a drop-in dependency.
- How do I install requestum/api-bundle?
- You would install it with Composer and register the bundle in a Symfony kernel, not in a Laravel application. The repository documentation is thin, so expect to read the source to understand configuration. Before installing, check composer.json constraints because the last release was in January 2021.
- What PHP and Symfony versions does requestum/api-bundle support?
- The package has not been released since January 2021, so its dependency graph likely targets PHP 7.4–8.0 and Symfony 4/5 era versions. There is no evidence of compatibility with PHP 8.2/8.3 or Symfony 6/7. Run composer why-not against your target versions before assuming it will install.
- What features does requestum/api-bundle provide for JSON APIs?
- It provides reusable base controllers, request helpers, standardized JSON response formatting, and centralized exception handling for API endpoints. The bundle also offers an extensible structure for pagination, validation, and custom logic. Its main value is enforcing consistent API contracts rather than offering a large feature set.
- Is requestum/api-bundle still maintained?
- There has been no release since January 2021, and the repository shows only 4 stars and 0 dependents. That suggests it is unmaintained and lacks community validation or upstream security patching. Treat it as an unproven artifact and plan for ownership if you adopt any part of it.
- Can I use requestum/api-bundle in production?
- Using it directly in production carries significant risk because it is abandoned, has a single maintainer, and has frozen framework constraints. The safer path is to vendor a fork under your namespace with CI, static analysis, and a named owner. For Laravel, do not add it as a dependency; reimplement the useful conventions with native Laravel primitives instead.
- What are Laravel alternatives to requestum/api-bundle?
- Laravel already provides API Resources for response formatting, the exception handler for error normalization, and packages like spatie/laravel-query-builder for filtering and pagination. Sanctum covers authentication, and Fractal is available for transformation layers. These native and maintained options cover the same concepts without the Symfony coupling or abandonment risk.
- Does requestum/api-bundle handle exceptions and error responses?
- Yes, centralized exception handling and standardized error payloads are core parts of the bundle. That said, it imposes its own envelope shape and status semantics, which are expensive to change after API consumers integrate. Review the response and error contracts carefully before committing to them.
- How do I test requestum/api-bundle or run its test suite?
- The repository does not advertise test coverage, so first check for a test suite and try running it against your PHP version. Expect compatibility issues if the code targets PHP 7.4/8.0. If you vendor a fork, add tests around response formatting and error semantics before relying on it.
- Can I fork or vendor requestum/api-bundle internally?
- Forking is the realistic adoption path, but you must first confirm the license and attribution requirements. Copy the audited commit into an internal packages directory or private VCS, rename the namespace, and update PHP and framework constraints. Wrap the fork behind internal interfaces so it can be replaced later without touching feature code.