Weave Code
Admin Ddd Extensions Bundle Laravel Package
lin3s/admin-ddd-extensions-bundle
Lin3s Admin DDD Extensions Bundle offers reusable Symfony components and conventions for building admin interfaces around domain-driven design applications, extending admin tooling with DDD-friendly abstractions and integration helpers.
lin3s/admin-ddd-extensions-bundle is a Symfony bundle that bridges a DDD-style application layer with an admin panel, offering reusable building blocks so back-office resources can be wired to domain commands and queries instead of raw entities. It targets projects already following Domain-Driven Design conventions, keeping admin code thin and decoupled from persistence concerns.
- Admin controllers and CRUD scaffolding built on top of command/query handlers
- Configuration-driven resource and form definitions for rapid back-office setup
- Integration with Symfony DI for automatic service wiring of admin extensions
- Conventions that keep domain, application and admin layers clearly separated
Frequently asked questions about Admin Ddd Extensions Bundle
- Is lin3s/admin-ddd-extensions-bundle compatible with Laravel?
- No. It is a Symfony bundle built as an extension layer for LIN3S/AdminBundle, so its service wiring, event hooks, and admin UI integration target Symfony, not Laravel. Laravel has no bundle mechanism and the package provides no service provider, publishable config, facade, or route registration. Any reuse in Laravel is conceptual or via a port, not a direct install.
- Can I install this bundle with Composer in a Laravel project?
- Composer installation is unlikely to succeed, and even a successful resolve would not give you a working Laravel integration. The package was last released in 2017 and almost certainly constrains Symfony components and PHP to old versions that conflict with Laravel 9+. Composer will typically fail on dependency resolution before runtime.
- What DDD features does lin3s/admin-ddd-extensions-bundle add to admin interfaces?
- The bundle is described as adding domain-driven design extensions to LIN3S admin interfaces, offering reusable building blocks that connect admin tooling with DDD patterns. The README excerpt in this evaluation is empty, so the exact primitives are not confirmed. You need to audit the source to identify command buses, repository interfaces, specifications, value-object bases, or collection types. Do not assume those features exist without inspecting the code.
- Does this package support PHP 8, Laravel 10, or Laravel 11?
- Almost certainly not. Its last release date is 2017-11-07, which places it in the PHP 5.6/7.0 and Symfony 2.7/3.0 era. Modern Laravel 10/11 requires PHP 8.1+ and Symfony 6/7 components. The package would need a substantial port before it could run on a current PHP/Laravel matrix.
- Is lin3s/admin-ddd-extensions-bundle maintained?
- No meaningful maintenance signal exists. The evaluation notes zero stars, zero dependents, and no release since 2017-11-07, which puts it in abandoned-project territory. There is no security response process, CI signal, or downstream user base to surface bugs. Adopting it means becoming the maintainer by default.
- What should I use in Laravel instead of this Symfony admin bundle?
- Use a Laravel-native admin panel such as Laravel Nova, Filament, or Backpack for the admin UI layer. Implement DDD primitives as framework-agnostic PHP classes in your application or an internal Composer package. Bind repository interfaces to Eloquent or Doctrine implementations through a Laravel service provider. There is no economic bridge between this bundle and Laravel admin tooling.
- Should I use lin3s/admin-ddd-extensions-bundle in production?
- No, not as a dependency. The technical risk is high: no releases in eight years, no maintainers, no security path, and near-zero Laravel feasibility. Any production adoption would require forking, an internal security review, and ongoing ownership. Treat it as prior art to mine rather than code to deploy.
- How do I port the DDD extensions from this Symfony bundle to Laravel?
- Clone or vendor the source and inventory every class, classifying each as pure PHP domain code, Symfony DI/HTTP wiring, or admin-UI coupling. Extract the pure domain code, such as value objects, specifications, typed collections, and repository interfaces, and republish it internally as a framework-agnostic package with a modern PHP constraint. Discard the Symfony bundle wiring and LIN3S Admin UI integration, then reimplement intent in a thin Laravel service provider. Add tests before any domain code depends on the port.
- What dependency conflicts will this bundle cause with modern Laravel?
- The blocking conflicts are Symfony component constraints and the PHP floor. A 2017 bundle will almost certainly require symfony/* in the 2.7 or 3.0 range and PHP 5.6 or 7.0, while Laravel 9+ needs Symfony 6/7 and PHP 8.1+. Composer resolution fails before you reach runtime, and forcing it would downgrade core framework components.
- Can I use this bundle as a reference for layering DDD over an admin CRUD UI?
- Yes, that is its best use. It can serve as prior art for how LIN3S connected DDD patterns to admin CRUD interfaces. Audit it to separate portable domain code from Symfony-specific and admin-UI-specific code. Then implement the patterns in your Laravel codebase rather than installing the package.
Weaver
How can I help you explore Laravel packages today?