Weave Code
Api Bundle Laravel Package
happyr/api-bundle
HappyR API Bundle is a PHP bundle that provides a reusable foundation for building APIs, helping you organize endpoints and standardize responses so you can ship consistent, maintainable API services faster.
HappyR ApiBundle is a Symfony bundle that provides a lightweight foundation for building JSON APIs. It helps organize API endpoints and responses within familiar Symfony conventions, making it easier to expose application data through consistent, client-friendly interfaces.
- Symfony-native integration with bundle configuration and services
- Structured JSON responses for API endpoints
- Controller conventions for organizing API logic
- Extensible design for project-specific API behavior
- Composer-ready installation for quick setup
Frequently asked questions about Api Bundle
- Can I use happyr/api-bundle in a Laravel application?
- Not as a normal dependency. happyr/api-bundle is a Symfony bundle built around Symfony's kernel, dependency injection extension, container, and event dispatcher; Laravel has no equivalent extension points. There is no Laravel service provider, config publish path, or Illuminate contract implementation. In Laravel, you would need to port or reimplement the behavior rather than install and configure it.
- What does happyr/api-bundle actually provide for REST APIs?
- It is a Symfony bundle for building REST APIs with less boilerplate. The described features include WSSE support, content negotiation, API versioning through Accept headers, request parameter conversion, and consistent JSON error responses. Annotations and event listeners are used to keep controllers thin and output predictable. Most of that value sits in Symfony-specific wiring, so it does not transfer directly to Laravel.
- How do I install happyr/api-bundle?
- In a Symfony project you would install it with Composer and register the bundle in the kernel, then configure its extension tree. In Laravel there is no package discovery, service provider, or config publish step to make it work. Composer may install the source, but it will not wire routes, middleware, or error handling for Laravel.
- Does happyr/api-bundle support Laravel 10 or Laravel 11?
- No. It is a Symfony bundle, not a Laravel package, and it was last released in 2018, well before Laravel 10 and 11. It has no Illuminate contracts, service provider, or Laravel config publish path. Supporting modern Laravel would require an adapter or a rebuild.
- How would I port happyr/api-bundle features to Laravel?
- Start by naming the exact behavior you need, such as error envelope normalization, Accept-header versioning, content negotiation, or request param conversion. Then bind any reusable core classes in a Laravel service provider, translate Symfony YAML config into a Laravel config file, and reimplement listener behavior as middleware. The expensive part is the event-listener layer, which is usually where the real value lives. For a narrow need, building roughly 200 lines in Laravel is often safer than vendoring the bundle.
- Is happyr/api-bundle maintained and safe for production?
- Treat it as unsafe to depend on for production. The last release was 2018-10-10, adoption is 1 star and 0 dependents, and there is no support channel, CVE response, or release cadence. The low score of 0.165 is directionally correct because it penalizes staleness and lack of ecosystem. If you fork it under MIT, you own all remediation.
- What PHP and Symfony versions does happyr/api-bundle require?
- The exact composer.json constraints should be read verbatim before any commitment. The 2018 release places it in the Symfony 3.4/4.x and PHP 7.0–7.2 era, so its symfony/framework-bundle range is likely to conflict with a modern stack. PHP 8.1+ deprecations such as dynamic properties and return-type variance are unpatched. Those constraints alone may be disqualifying.
- Does happyr/api-bundle have tests or documentation?
- The evaluation does not confirm a test suite or strong documentation, and with 1 star and 0 dependents there is no downstream usage corpus to learn from. With zero maintainers, tests would be the only proxy for the package's spec. Check the repository directly for tests and confirm what behavior they cover before relying on any of it.
- What are alternatives to happyr/api-bundle for Laravel API development?
- For Laravel, use native middleware for content negotiation and API versioning, API Resources for response shaping, Form Requests for parameter conversion, and the exception handler for consistent JSON errors. Laravel Sanctum or Passport covers auth, and query-builder packages can handle filtering and pagination. Only port the Symfony bundle if it has a specific edge-case behavior you cannot reproduce cleanly.
- Should I fork happyr/api-bundle or rebuild the features in Laravel?
- Rebuild in Laravel by default, using happyr/api-bundle as source material and a reference for domain modeling and edge cases. Fork only if you have identified a specific, tested behavior worth preserving and accept ownership of security fixes and releases. MIT gives you the legal right to fork, but it gives you no support channel or maintenance commitment. A short conversation with Happyr about a Laravel-oriented fork or transfer could change that calculus.
Weaver
How can I help you explore Laravel packages today?