- Does rikudou/json-api-bundle work with Laravel?
- No. It is a Symfony bundle, not a Laravel package. It has no Laravel service provider, no package auto-discovery, and no publishable config, so using it in Laravel means manually porting its Symfony service definitions or pulling Symfony components into your app. For a Laravel codebase, evaluate a Laravel-native JSON:API implementation instead.
- How do I install rikudou/json-api-bundle?
- Install it with Composer and register the bundle in your Symfony application's bundle configuration. You then configure it through Symfony bundle configuration and dependency injection services. There is no Laravel-style vendor:publish or auto-discovery step, so plan for manual wiring.
- Which JSON:API features does this bundle actually implement?
- The documented scope covers resource serialization into JSON:API documents with attributes and relationships, compound documents with automatic included resolution, and relationship handling for to-one and to-many links. The blurb also mentions filtering, pagination, and standardized error responses, but the README is thin. Verify sparse fieldsets, includes, sorting, filtering, pagination, and error objects directly in the source and tests before relying on them.
- Is rikudou/json-api-bundle actively maintained?
- Public signals show a single maintainer, zero stars, zero dependents, and no visible production adoption. That does not prove poor quality, but it means release cadence, issue responsiveness, and long-term support are unknown. Check the repository's commit history and CI status before committing to it.
- What PHP and Symfony versions does it support?
- The authoritative answer is in composer.json, not in blog posts or the README. Check the PHP and Symfony version constraints against your exact minor versions and watch for deprecation warnings under your framework version. Attribute names such as ApiResource, ApiId, and ApiAttribute have shifted between versions, so read the source for your pinned release.
- Can I use rikudou/json-api-bundle in production?
- Treat it as high risk. The main concerns are framework mismatch if your target is Laravel, bus-factor-one abandonment, version lockout at the next PHP or Symfony upgrade, and silent JSON:API spec drift that breaks clients subtly. It is MIT licensed, so a throwaway evaluation branch costs little, but scope any trial to one bounded-context resource collection before expanding.
- What are the alternatives to rikudou/json-api-bundle for JSON:API?
- For Laravel, look at Laravel-native implementations such as laravel-json-api. For a framework-agnostic approach with lower coupling, consider neomerx/json-api or the underlying rikudou/json-api serializer library that this bundle wraps. The bundle is mostly Symfony wiring, so the standalone serializer is the lower-risk fallback if you need the same behavior.
- Do I need to write custom normalizers with this bundle?
- The bundle is extensible through normalizers for custom resource types, so standard resources may work with the built-in behavior. Non-standard resources, custom IDs, or unusual relationship shapes will likely require your own normalizer classes. Budget time to read the bundle's service configuration and tests to understand the extension points.
- How does it handle relationships and the included section?
- It serializes to-one and to-many relationships and automatically resolves compound documents into the included array. That is useful for spec-compliant responses without hand-crafting payloads. Because the README is thin, test compound documents and relationship links against the JSON:API specification before trusting them in client contracts.
- Is rikudou/json-api-bundle MIT licensed, and can I fork it?
- Yes, the MIT license allows forking and commercial use. However, with zero dependents and a single maintainer, a fork makes your team the de facto maintainer of that code. Factor ongoing maintenance and upgrade work into the decision rather than treating the license as a free pass.