Weave Code
Ember Eloquent Laravel Package
nuwave/ember-eloquent
Bridges Ember and Laravel's Eloquent ORM, giving Ember apps a clean way to expose models through Eloquent-backed APIs with consistent serialization and conventions.
At a glance
Frequently asked questions about Ember Eloquent
- What is nuwave/ember-eloquent used for?
- It is a Laravel package for exposing Eloquent models to Ember Data through consistent, Ember-friendly API payloads. It helps serialize models and relationships, including sideloading and nested payloads, so Ember apps receive the shape they expect. It is most useful when a Laravel API backs an Ember frontend and you want less custom serialization glue.
- How do I install nuwave/ember-eloquent in a Laravel app?
- Install it with Composer using composer require nuwave/ember-eloquent. It presents as a conventional Laravel package with service provider registration and publishable configuration, so expect a provider entry or auto-discovery plus a config publish step. Resolve it in a branch of your real application first because Composer constraints can conflict with your lockfile.
- Do I need to publish a config file for Ember Eloquent?
- The package includes publishable configuration, so you will likely run vendor:publish for the package config during setup. Review the published options in a pull request before adopting it, because the config surface is part of your integration risk. If defaults are sufficient, you may be able to adopt it without customizing much.
- Which Laravel and PHP versions does nuwave/ember-eloquent support?
- The provided context does not list a declared Laravel or PHP support matrix, so check the package composer.json and CI configuration directly. The 1.3.2 release implies a stable 1.x line, and pinning to ^1.3 is reasonable once compatibility is confirmed. Verify the constraints against your current and next-planned Laravel upgrade before committing.
- How does Ember Eloquent handle relationship sideloading?
- The package is designed to serialize Eloquent models and their relationships into Ember Data payloads, including sideloaded and nested relationship data. That reduces the amount of custom code needed to map Laravel models to Ember's expected JSON shape. You should still test representative relationship graphs, because sideloading behavior can vary by endpoint and serializer configuration.
- How should I test nuwave/ember-eloquent in my Laravel application?
- Test it through your own application endpoints rather than only in a scratch project, using production-shaped models and relationships. Exercise at least one representative create, update, and relationship-loading path to confirm the payload shape matches your Ember models. The package's own test and CI coverage is not detailed in the provided context, so review the repository before relying on it.
- Is nuwave/ember-eloquent safe for production use?
- It is a conventional Laravel Composer package, but the context flags governance and verification items rather than confirmed defects. Before production, confirm the 1.3.2 change diff, Laravel and PHP support, dependency footprint, license, and test coverage. Roll it out behind a feature flag and compare payloads against your current implementation if you are replacing existing serialization.
- What are alternatives to nuwave/ember-eloquent for Ember Data APIs in Laravel?
- Alternatives include hand-built Laravel API Resources, Fractal transformers, or JSON:API-oriented packages, depending on how closely you need Ember Data conventions. Ember Eloquent is specifically aimed at Ember-friendly serialization and relationship sideloading, so it may save glue code compared with a generic transformer. Evaluate alternatives against your payload contract and maintenance requirements.
- Why are the 1.3.2 release notes empty, and does that matter?
- An empty changelog on a patch release is a governance signal, not proof of a breaking change; semver says patch releases should be compatible, but it is only a convention. Read the compare diff for 1.3.2 rather than relying on release notes. Also check issue-response history and maintainer activity before pinning it in production.
- How do I avoid Composer dependency conflicts with nuwave/ember-eloquent?
- Install it in a branch of your real application so Composer resolves against your existing lockfile, not an empty scratch project. Pin to ^1.3 and avoid floating to * or dev-main, then inspect the resolved illuminate/* and transitive dependencies for conflicts or unmaintained packages. If it blocks your next Laravel upgrade, treat that as a migration cost before adopting.
Weaver
How can I help you explore Laravel packages today?