Weave Code
Rest Api Bundle Laravel Package
kununu/rest-api-bundle
kununu/rest-api-bundle is a Symfony bundle for PHP that packages reusable infrastructure and conventions for building REST APIs, helping teams standardize endpoints, request handling, and responses across services.
This is a wrapper for mediamonks/rest-api-bundle adding kununu specific functionality.
Frequently asked questions about Rest Api Bundle
- Is kununu/rest-api-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It registers through Bundle::class in config/bundles.php and participates in the Symfony container build via Extension and CompilerPass classes. Laravel has no equivalent bundle boot contract, and its service providers, middleware pipeline, and container semantics are deliberately different. The package is also an explicit fork that wraps mediamonks/rest-api-bundle and adds kununu specific functionality.
- Can I install kununu/rest-api-bundle in a Laravel application?
- Composer may resolve it, but that is not integration. Making it work would mean standing up Symfony's DI container and kernel boot inside a Laravel app, or extracting the underlying classes and rewiring them by hand. Both are net-new engineering, and the Symfony-major coupling likely causes transitive dependency conflicts with the Symfony components Laravel already ships. For a Laravel 10 or 11 stack, the honest recommendation is do not integrate.
- Which Laravel versions does kununu/rest-api-bundle support?
- None officially. There is no Laravel service provider, no facade, and no published configuration contract aimed at Laravel consumers, so there is nothing for a Laravel version to be compatible with. The repository naming and wrapper pattern suggest a Symfony 3 or 4 era lineage, which is well outside a modern Laravel 10 or 11 dependency tree. If your target is Symfony, the assessment changes entirely and this may be a plausible drop-in.
- Is kununu/rest-api-bundle on Packagist and what license does it use?
- You need to verify this yourself, because a public repository and an installable Composer dependency are different claims. Check the Packagist listing and the license declared in composer.json before planning anything around it. If the license is permissive, that at least keeps a pattern port or a vendored copy legally straightforward. If it is not published, your only realistic option is reading the source as a reference implementation.
- What does the kununu layer actually add on top of mediamonks/rest-api-bundle?
- The package describes itself only as kununu specific functionality layered on the parent bundle, so the exact additions are not documented in the overview. Likely candidates are the response envelope shape, error formatting, versioning headers, and auth middleware conventions, but you should confirm by reading the source. Treat those behaviors as a specification you can reimplement rather than code you can depend on. The transferable asset here is the design pattern, not the implementation.
- How do you install and configure kununu/rest-api-bundle in a Symfony project?
- In Symfony the usual path is a Composer require, then registering the bundle in config/bundles.php and configuring it through its Extension class. You should first check the PHP and Symfony version constraints declared in composer.json, since the fork inherits the parent bundle's constraints and adds a maintenance layer of its own. There is no equivalent Laravel setup path, no facade, and no config file published for Laravel consumers.
- Is kununu/rest-api-bundle maintained and safe to run in production?
- The signals are weak: no stars, a composite score of zero, and zero dependents, meaning no external population is exercising this code. That means no de facto compatibility testing and no evidence it works outside kununu's own estate. A wrapper also inherits its parent's constraints, so your security posture is capped by whether mediamonks/rest-api-bundle is still maintained. Assume there is no expectation of external support and plan accordingly.
- What are the Laravel alternatives to kununu/rest-api-bundle for building REST APIs?
- Laravel already covers this ground with first-class support: API Resources for response transformation, form requests for validation, middleware for headers and versioning, and JsonResponse macros for consistent envelopes. If you want dedicated transformer layers, spatie/laravel-fractal or league/fractal are established options. These give you the same structured response and serialization behavior without dragging in a Symfony kernel. The kununu package is better read as a reference for conventions than used as a dependency.
- How do I port kununu/rest-api-bundle conventions into a Laravel app?
- There is no migration path, because there is nothing to migrate from, so do a pattern port instead. Read the kununu and mediamonks source, extract the response envelope contract plus any error and versioning conventions, then reimplement them as Laravel middleware and JsonResponse macros or API Resource classes. If the kununu-specific behavior is genuinely small, vendoring a handful of classes under app/Support with an adapted-from attribution header is cheaper and safer than a Composer dependency.
- How should I test a Laravel REST API layer inspired by kununu/rest-api-bundle?
- Since the package itself gives you no compatibility testing in Laravel, test your reimplementation directly. Use Laravel's HTTP test helpers in feature tests to assert the JSON envelope shape, error formatting, versioning headers, and status code behavior for each endpoint. Add contract tests that pin the response structure so future refactors cannot silently change it. That gives you coverage the original fork never had outside its own company's estate.
Weaver
How can I help you explore Laravel packages today?