Weave Code
Ng Admin Generator Bundle Laravel Package
marmelab/ng-admin-generator-bundle
A Symfony bundle that generates ng-admin back-office configurations from Doctrine entities, automatically mapping fields and relations to CRUD views and forms so you can expose admin panels with minimal boilerplate.
Generate a client-side admin backend for Symfony2 applications, powered by ng-admin and LemonRestBundle
Frequently asked questions about Ng Admin Generator Bundle
- Is marmelab/ng-admin-generator-bundle a Laravel package?
- No. It is a Symfony bundle that introspects Doctrine entity metadata and LemonRestBundle annotations, then emits a JavaScript configuration file for ng-admin. Every layer of its stack, including bundle registration, Doctrine mappings, and AngularJS output, is orthogonal to Laravel, Eloquent, Artisan, and Blade. Treat it as a reference implementation to study rather than a dependency to install in a Laravel application.
- Can I install ng-admin-generator-bundle in Laravel with Composer?
- Composer may resolve the package, but installing it does nothing useful because Laravel has no Symfony bundle concept to register the compiler passes and service definitions. You would need a service provider shim that manually re-registers the generator classes, and the generator would still read Doctrine and LemonRest metadata that a Laravel app does not have. There is no adapter layer in the package, so the value proposition does not transfer out of the box.
- What does ng-admin-generator-bundle actually generate, and what does it need to run?
- It generates an ng-admin configuration file that maps Doctrine entities and their relations to AngularJS 1.x CRUD views and forms. It requires a Symfony application exposing an API through LemonRestBundle, plus the Doctrine annotations that describe fields and associations. The output is a client-side admin front end, not PHP admin scaffolding, so it brings a separate JavaScript toolchain into your project.
- Does ng-admin-generator-bundle support Laravel 10, 11, or PHP 8?
- No. The package targets the Symfony 2 and 3 era and is archived upstream, with no guarantee of PHP 8.x support. There is no Laravel version compatibility matrix because Laravel was never a supported target. If you need PHP 8.2+ and current Laravel, plan on owning a fork rather than relying on the published package.
- Is ng-admin-generator-bundle still maintained?
- No, the upstream repository is archived and unmaintained, with zero dependents and no fork ecosystem to lean on for fixes. It also carries a phantom dependency on the similarly legacy LemonRestBundle, which compounds the abandonment risk. That means no security patches and no community validation, so any use requires an explicit maintenance budget on your side.
- Can I fork ng-admin-generator-bundle and drive it from an Artisan command?
- Yes, that is the only realistic integration path, but expect to vendor the generator classes into app/Console/Commands or an internal packages directory and invoke them from something like php artisan admin:generate-config. You would replace Doctrine metadata reads with Eloquent equivalents such as Schema::getColumns, casts, fillable, and relationship methods. The field-type mapping table is the real work and you will hand-write and own it indefinitely.
- How do I map Eloquent models and relationships to ng-admin fields?
- The bundle ships logic that maps Doctrine types to ng-admin field directives such as boolean, date, reference, embedded, and choice, but there is no Eloquent equivalent for polymorphic relations, JSON columns, or enum casts. You would need to build that mapping table yourself and decide how hasMany, belongsToMany, and morphMany relations render as embedded lists or reference fields. Budget for this mapping layer to be the bulk of the port effort.
- Does the generated ng-admin config handle authentication, policies, or multi-tenancy?
- No. The generator has no notion of Laravel policies, gates, or tenancy scopes, and it emits a static client-side configuration rather than server-enforced rules. Shipping a generated admin config without authorization modeling is a security liability, not a time-saver, because the admin CRUD surface is a prime attack target. You would have to add authorization in the API layer regardless of which admin tool you choose.
- What are the Laravel-native alternatives to ng-admin-generator-bundle?
- Filament, Laravel Nova, and Backpack all provide schema-driven admin panels that are Laravel-native, actively maintained, and aware of Eloquent relationships and policies. If your actual need is schema-driven form scaffolding rather than a full admin UI, Artisan make:model and make:resource scaffolding already covers it. For most teams the port cost of this bundle exceeds simply adopting one of those tools.
- Is shipping an AngularJS 1.x ng-admin front end a production risk in a new Laravel app?
- Yes. AngularJS 1.x reached end-of-life in December 2021, so the generated admin inherits an unsupported front-end framework with no security patches. It also sits outside the Laravel asset pipeline, pulling in a Node and Bower-era build that your team must maintain separately. If you are not willing to run an AngularJS single-page app, the generator's output is unusable regardless of how well you port the PHP side.
Weaver
How can I help you explore Laravel packages today?