Weave Code
Server Crud Bundle Laravel Package
modera/server-crud-bundle
Modera Server CRUD Bundle is a PHP package for quickly scaffolding server-side create, read, update, and delete workflows. It helps organize resource controllers, request handling, and data operations for admin panels and APIs.
[READ-ONLY] Provides tools that simplify building heavily data-driven applications.
Frequently asked questions about Server Crud Bundle
- Is modera/server-crud-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. The package name, the Bundle and DependencyInjection lifecycle, and the Doctrine-based persistence all point to Symfony 2.x-era conventions. There is no Laravel service provider, Eloquent integration, Artisan command, or Blade, Inertia, or Livewire contract anywhere in the source. If it showed up on a Laravel shortlist, that is a framework-tagging error in the sourcing pipeline rather than a genuine match.
- Can I install modera/server-crud-bundle in a Laravel 10 or 11 app with Composer?
- Practically, no. Requiring it into a modern Laravel app on PHP 8.2+ collides with the Symfony component versions Laravel already pulls in, and the source predates modern typing conventions, so it can fatal-error on PHP 8.x. Nothing in Laravel's container or HTTP kernel knows how to boot a Symfony bundle. Even a forced install would leave you with a dependency you cannot wire up.
- What PHP and Symfony versions does modera/server-crud-bundle target?
- The bundle targets the Symfony 2.x era, with assumptions such as early PSR-4 or PSR-0 autoloading and legacy Doctrine hydration APIs. Its last tagged release was 10 June 2016. That predates Symfony 3 and 4 entirely, and it has never been updated for modern PHP versions. Treat it as a legacy PHP 5.x and 7.x artifact.
- Is modera/server-crud-bundle still maintained?
- No. The repository mirror is marked READ-ONLY, the last release dates to June 2016, and there is no maintainer activity or downstream consumer signal. It has roughly two GitHub stars and zero Composer dependents. Every bug you hit becomes yours permanently, because there is nobody upstream to fix it.
- What does modera/server-crud-bundle actually provide?
- It provides a reusable CRUD controller abstraction with generic list, get, create, update, and delete actions. On top of that sits a configuration object declaring the entity, allowed actions, ignored fields, and per-action security, plus a pluggable handler chain for validation, persistence, and response shaping. The value is the application-layer pattern, not a portable library. It also assumes an ExtJS and Sencha-style grid payload contract for list endpoints.
- What Laravel packages should I use instead for CRUD backends?
- For admin panels and resource UIs, Filament and Laravel Nova cover the same ground natively. For API list endpoints with filtering, sorting, and includes, spatie/laravel-query-builder gives you a declarative DSL that maps closely to what this bundle did. Laravel's own resource controllers and route model binding handle the rest of the CRUD scaffolding. All of them are maintained, tested against current Laravel releases, and install cleanly.
- Is it safe to use modera/server-crud-bundle in production?
- No. A 2016 Symfony 2.x dependency graph carries known, unpatched CVEs, and upgrading those components means forking and rewriting the bundle internals. You also inherit a second security model if you run it alongside a modern application. The maintenance risk alone, with no releases in about nine years and zero dependents, makes it unsuitable for anything long-lived.
- Can I reuse the CRUD pattern from this bundle in Laravel without the dependency?
- Yes, and that is the only sensible approach. Read the controller, config, and handler contracts, then reimplement the subset you need natively using Laravel resource controllers, form requests, and policies. The transferable pieces are the declarative filter, sort, and include DSL parsed from query parameters and the consistent list-response envelope. Porting a few hundred lines of design intent is far cheaper than maintaining a legacy Symfony runtime.
- How would I test code built on the bundle's controller and handler contracts?
- Test the handler chain in isolation, since validation, persistence, and response shaping are separate collaborators that can be mocked. The controller itself is thin, so most coverage belongs in unit tests around each handler plus a small number of functional tests on the list endpoint. If you port the pattern to Laravel, feature tests with RefreshDatabase and unit tests on the query-parameter parser give you equivalent confidence.
- Does modera/server-crud-bundle work with Eloquent, or only Doctrine?
- Only Doctrine. The bundle was written against Doctrine ORM hydration and Symfony's entity manager, and there is no Eloquent, query-builder, or Laravel model abstraction in the codebase. Eloquent's fluent API and Doctrine's Unit of Work are not interchangeable, so the persistence handlers would need rewriting rather than adapting. If your application is Eloquent-based, plan on a native implementation.
Weaver
How can I help you explore Laravel packages today?