- What does morontt/doctrine-to-ember actually do?
- It reads Doctrine2 entity metadata and generates Ember Data model classes so your frontend schema stays aligned with your backend. The package ships as a Symfony bundle (DoctrineToEmberBundle) registered through Symfony's kernel and DI extension mechanism. It targets the Symfony 2/3 and Doctrine 2.x era rather than modern Ember Data or WarpDrive conventions.
- Can I use morontt/doctrine-to-ember in a Laravel application?
- No, not without forking it. Laravel has no Symfony bundle loader, so there is no service provider, no extra.laravel auto-discovery, and no publishable config. On top of that, the package assumes a Doctrine2 ORM persistence layer while Laravel defaults to Eloquent, and the bundle's compiler passes still will not load even if you add Doctrine via laravel-doctrine/orm.
- How do I install morontt/doctrine-to-ember?
- The documented path is Composer plus manual registration of DoctrineToEmberBundle in a Symfony AppKernel, followed by bundle configuration. There is no Laravel installation path, no Artisan command, and no config file you can publish. In a Laravel project the only realistic option is vendoring the source and porting the metadata-reflection logic out of the Symfony container.
- Does this package support Laravel 10 or Laravel 11?
- No. The package predates modern Laravel entirely and offers no Laravel version support, no service provider, and no framework integration hooks. It also dates from the Symfony 2/3 era, so treat any published PHP constraints as stale and assume PHP 8.2+ will surface deprecations or fatal errors.
- Does it work with Eloquent models instead of Doctrine entities?
- No. The generator depends on Doctrine2 ORM entity metadata, so Eloquent models are invisible to it. Even if you run Doctrine in Laravel through laravel-doctrine/orm, the package's Symfony compiler passes and container wiring still cannot be loaded, so resolving the persistence mismatch alone does not make it usable.
- Is morontt/doctrine-to-ember still maintained?
- No. The repository is archived, has roughly 3 stars and 0 dependents, and has no CI signal or release matrix. There is no security response process, no upstream to rebase against, and no downstream community that has validated it in production. Adopting it means owning an unmaintained fork indefinitely.
- What are the alternatives to doctrine-to-ember for generating frontend models?
- Build a thin generator in-house rather than porting this bundle. An Artisan command that reads Eloquent model metadata (or Doctrine metadata via laravel-doctrine/orm) and emits JSON:API schema, TypeScript interfaces, or Ember/WarpDrive model classes is a matter of days of work. For non-Ember clients needing JSON:API, maintained serializers are a better fit than this package.
- Can I use it with laravel-doctrine/orm to get Doctrine in Laravel?
- No. Installing Doctrine in Laravel does not make a Symfony bundle registerable, because the bundle relies on Symfony kernel bootstrapping and DependencyInjection compiler passes that Laravel does not run. The only path is vendoring the source and hand-porting the metadata-reflection logic into a service or Artisan command. That is a rewrite of the integration surface, not an integration.
- How do I generate Ember Data models from a Laravel backend?
- Write a small Artisan command that inspects your models and outputs the target artifact, whether that is Ember/WarpDrive classes, JSON:API schema, or TypeScript types. Add a CI drift check so the build fails when the backend schema changes without a matching frontend update. That drift check, not the converter, is where the durable value sits.
- Is morontt/doctrine-to-ember safe to run in production?
- The technical risk is high. There are no PHP 8.x compatibility guarantees, no security response, no CI results, and no dependents that have validated it in production. If you need this capability, reimplement the pattern in-house and record the decision explicitly so the request is not raised again.