- Is pdfloresjdav/api-bundle a Laravel package or a Symfony bundle?
- The description claims Laravel-native integration, but the ApiBundle naming and Pdfloresjdav\ApiBundle namespace follow Symfony bundle conventions. Those conventions are not interchangeable: a Symfony Bundle class is inert in Laravel, and a Laravel service provider does nothing in Symfony. Check composer.json for illuminate/* versus symfony/framework-bundle before treating it as Laravel-compatible.
- How do I install pdfloresjdav/api-bundle in a Laravel application?
- The expected path is a Composer require followed by service provider discovery or manual registration, but the package has no documented install history in the provided context. Install it into a throwaway Laravel app first and confirm that Composer resolves framework constraints and that the provider boots. Do not add it to a shared branch until that spike succeeds.
- Does api-bundle support Laravel 10 or Laravel 11?
- Laravel version support cannot be confirmed from the package description alone. The composer.json illuminate/* constraints are the only reliable answer, and there is no visible release history to infer from. Treat any specific Laravel version claim as unproven until you inspect those constraints.
- What does api-bundle do that Laravel's Route::apiResource and JsonResource do not?
- The package claims bundle registration, organized routing, thin controllers, request validation, and consistent JSON responses. Laravel already covers most of that with Route::apiResource, FormRequest, JsonResource, ResourceCollection, and the default exception handler. The real question is whether the bundle convention saves enough boilerplate to justify an extra dependency.
- How do I register a bundle or configure routes with api-bundle?
- The overview mentions bundle registration, PSR-4 namespaces, and service provider hooks, but the exact public API is not shown in the excerpt. Read the service provider or DI extension to see how routes, config merging, and publishing are wired. If the package ships a Symfony extension instead of a Laravel provider, route registration will not work as described.
- Is pdfloresjdav/api-bundle safe to use in production?
- There is no adoption evidence: zero stars, zero dependents, no release history, and no visible maintenance cadence. An unvetted Composer dependency executes code at install and boot, so it needs composer audit, a license check, and a source review before it touches production. Without that review it is an evaluation artifact, not a production dependency.
- Does api-bundle handle request validation and consistent JSON error responses?
- The blurb says it includes request validation and standardized JSON responses out of the box. Laravel already provides FormRequest validation and JSON rendering through its exception handler, so confirm what shape the package enforces. A competing error envelope or response convention can create friction alongside framework-native code.
- How do I test an API built with api-bundle?
- There is no visible test suite or CI configuration to rely on, so plan to write your own feature tests against the registered routes. Laravel's HTTP testing helpers can exercise the endpoints once the package boots in a test application. Keep the spike isolated so a failed boot does not affect your main test suite.
- What are the alternatives to api-bundle for structuring Laravel APIs?
- Laravel's first-party tools cover most of the same ground: apiResource routes, resource controllers, FormRequest, API Resources, route groups, and a custom exception renderer. For teams that want reusable scaffolding, in-house stubs or a small internal package are often cheaper to maintain. Evaluate those before adopting an unmaintained third-party bundle.
- Who maintains api-bundle, and what license and dependencies does it use?
- The available context points to a single maintainer with no stated support commitment and no activity history. The license and transitive dependencies are unknown until you read composer.json and run composer audit. With a bus factor of one, any breakage becomes your responsibility, so plan to fork or vendor it if you adopt it.