- Is enm/json-api-server-bundle a Laravel package?
- No. It is a Symfony bundle that integrates the framework-agnostic enm/json-api-server core into a Symfony kernel. It depends on Symfony bundle registration, YAML configuration, routing XML imports and container service tags, none of which exist in Laravel. For a Laravel application the architecture fit is effectively zero.
- Can I install enm/json-api-server-bundle in a Laravel application?
- Composer may resolve the package, but there is no service provider, no bundle bootstrapping, and no Laravel equivalent for the json_api_server.request_handler service tag. You would end up rewriting the entire Symfony glue layer, which is the only thing this package adds on top of the core library. Treat it as a design reference for a Laravel-native implementation rather than a dependency.
- Is enm/json-api-server-bundle still maintained?
- No. The last release was 2018-09-27, the repository is archived, and its build badge points at the now-defunct Travis CI service. It has roughly 10 stars and zero dependents, so there is no Stack Overflow corpus, no blog coverage and no hiring pool. With no maintainer there is also no security advisory or CVE response path.
- What does enm/json-api-server-bundle actually do?
- It wires enm/json-api-server into Symfony: bundle registration in config/bundles.php, optional YAML settings for debug, url_prefix and route_name_prefix, predefined JSON:API routes imported from routing.xml, and request handlers registered through the json_api_server.request_handler service tag keyed by resource type. It also adds built-in error handling for the standard JSON:API endpoints. All of its value lives in that Symfony glue.
- How do I install and configure it in a Symfony project?
- Run composer require enm/json-api-server-bundle, then register EnmJsonApiServerBundle in config/bundles.php for all environments. Optionally add config/packages/enm_json_api.yaml to set debug, url_prefix and route_name_prefix. Import @EnmJsonApiServerBundle/Resources/config/routing.xml in your routes file to get the predefined GET, POST, PATCH and DELETE routes.
- How are request handlers and routes registered?
- Handlers are ordinary services tagged with json_api_server.request_handler, where the type attribute holds the JSON:API resource type that handler serves. Routing typically comes from the bundle's routing.xml, which maps GET /{type}, GET /{type}/{id}, relationship endpoints and the write verbs onto a single jsonApiAction. If you add a URL prefix or route name prefix, you must mirror those values in the bundle's YAML config.
- Which PHP and Symfony versions does it support, and will it run on PHP 8.2?
- It is a Symfony 3.4/4.x-era package with composer constraints around PHP 7.x. Expect breakage on PHP 8.1/8.2 and Symfony 6/7 through deprecations, return type changes and container compilation passes, and note that 3.0.0 already churned internals by removing ResourceProviderPass, JsonApiLoader and JsonApiServerDecorator. Laravel version support is not applicable because it ships no Laravel integration at all.
- Does it support JSON:API 1.1?
- No. It implements JSON:API 1.0-era semantics, and the 1.1 specification published in 2022 is unsupported. Client tooling increasingly assumes 1.1 behaviour, so spec drift is a real risk. If a partner contract mandates JSON:API, confirm which version before relying on this package.
- What are the production and security risks of depending on it?
- Abandonment is the headline risk: no maintainer, no advisory process and no CVE response path, so you inherit the full transitive dependency tree with no upstream to patch it. Pinning to end-of-life PHP and Symfony blocks every future platform upgrade and compounds technical debt. Documentation lives only on the organisation's GitHub Pages domain, so reference material disappears if that lapses.
- What should Laravel developers use instead for JSON:API?
- Use a maintained Laravel-native JSON:API package, or build a thin resource and serializer layer with a documented error format. API Platform ships native JSON:API support on Symfony if the Symfony path is viable. If you are committed to Symfony, fork and vendor this bundle internally with your own CI rather than pulling it from Packagist in production.