Weave Code
Easy Api Platform Laravel Package
eonx-com/easy-api-platform
EonX Easy API Platform is a Laravel/PHP package that simplifies integrating API Platform into your app. It streamlines configuration and reduces boilerplate so you can expose consistent, standards-based REST and GraphQL APIs faster with less custom wiring.
[READ-ONLY] Provides features for API Platform applications
Frequently asked questions about Easy Api Platform
- What is eonx-com/easy-api-platform and what does it actually do?
- It is an opinionated conventions layer published by EonX that sits on top of API Platform and streamlines configuration while reducing boilerplate. The goal is to help you expose consistent, standards-based REST and GraphQL APIs with less custom wiring. It does not replace API Platform itself, so it only makes sense in an application that has already committed to API Platform. Note that this artifact is a read-only subtree split from a vendor monorepo, not a standalone project.
- How do I install eonx-com/easy-api-platform with Composer?
- It is a standard Composer package under the MIT license, so installation is a composer require with no procurement or legal gate. The install itself is trivial and tells you nothing about whether the package fits, so budget the real effort for a verification spike. Because the split carries no independent documentation in this listing, confirm the required service provider registration and any config publishing steps directly against the repository before wiring it into an app.
- Does eonx-com/easy-api-platform work with Laravel or is it Symfony-only?
- API Platform is Symfony-first, so the underlying framework matters more than the package label. EonX does publish dual-framework easy-* libraries, which suggests a Laravel bridge may exist, but that must be verified in the code rather than assumed. If your estate is a Laravel monolith with hand-rolled controllers and no API Platform commitment, this package solves a problem you do not have. Record that conclusion in a decision note so it stops resurfacing in every dependency review.
- Which PHP, Laravel, and API Platform versions are supported?
- Version support is not documented in this listing, so read the composer.json constraints in the split and confirm which combinations are genuinely exercised. Ask specifically whether Laravel is first-class or incidental, and which API Platform major the conventions target. Then prove it with a spike on your actual PHP and framework versions rather than trusting the constraint ranges.
- How much does it add on top of what API Platform already does natively?
- The package claims streamlined configuration and reduced boilerplate for filtering, pagination, serialization, and OpenAPI generation conventions. The only reliable way to size the benefit is a written feature inventory diffed against current native API Platform behavior. If most of the surface duplicates what the framework now ships, the maintenance line item is not worth the coupling. Keep that diff as the artifact a technical lead reviews before approval.
- Is eonx-com/easy-api-platform actively maintained?
- Adoption signal is weak: zero stars, zero dependents, and a read-only subtree split mean there is no independent release narrative, no package-specific issue tracker, and no community finding bugs before you do. Bus factor is effectively one vendor, and abandonment risk exists if the split stops being published. The offsetting factor is a small, auditable surface area that is cheap to fork, which downgrades abandonment from a crisis to a maintenance line item. Tests may or may not be included in the split, so check whether they ship and whether they run.
- Is it safe to use in production?
- Technical risk here is high, but it is driven by adoption signal rather than obvious code quality problems. The main concerns are vendor bus factor, undocumented breaking behavior on API Platform major bumps, and convention coupling that is hard to excise once call sites reference it. Because the surface is small and forkable at low cost, the sensible move is to price the risk explicitly in your risk register rather than leave it implicit. Treat feasibility as a timeboxed spike output, not a planning assumption.
- How should I evaluate fit before adopting it?
- Run a single one-week spike with one senior engineer against three representative endpoints. Produce a written feature inventory and a diff against what API Platform does natively today, plus a note on removal cost. That artifact, not the composer require, is what should drive the decision. Keep the strategic question of standardizing on API Platform separate from the tactical question of adding this dependency, since only the first is roadmap-shaping.
- How hard is it to remove eonx-com/easy-api-platform later?
- Convention libraries are difficult to excise once many call sites reference them, so plan for reversibility from day one. Introduce it behind existing configuration, enable one feature at a time, and isolate the diff to a single service provider or config block. Wrap or alias any classes that would otherwise be referenced broadly and forbid its conventions from leaking into domain code. Done that way, the exit ramp is a deleted provider plus a reimplementation behind the same interfaces.
- What alternatives should I consider instead of this package?
- The baseline alternatives are native API Platform configuration and a hand-rolled controller layer in Laravel, both of which avoid a third-party conventions dependency. If API Platform is already committed and you simply want less boilerplate, evaluate this package against writing the conventions in-house, which is feasible given the small surface. If API Platform is not committed, the honest alternative is to not adopt it at all and close the evaluation with a one-line decision record.
Weaver
How can I help you explore Laravel packages today?