Weave Code
Crud Bundle Laravel Package
gibilogic/crud-bundle
Gibilogic CRUD Bundle is a Symfony bundle that provides reusable CRUD scaffolding, helping developers quickly build create, read, update, and delete workflows with less boilerplate. It streamlines admin interfaces and backend management pages, making it easy to expose entity management in Symfony ap...
A Symfony 2 bundle that contains simple CRUD-oriented services and helpers
Frequently asked questions about Crud Bundle
- Is gibilogic/crud-bundle a Laravel package?
- No. It is a Symfony 2 bundle, declared as type symfony-bundle, and bundles are a Symfony kernel-level concept that Laravel does not consume. Laravel's extension surface is the service provider plus package discovery under extra.laravel, neither of which exists here. There is no auto-registration and the bundle's dependency injection extension cannot be read by Laravel's container. For a Laravel application the only realistic options are porting the logic or using the code as a reference.
- Can I install gibilogic/crud-bundle with Composer in a Laravel project?
- A composer require may succeed on name resolution, but installing it accomplishes nothing in Laravel because nothing registers routes, views, or services automatically. You would have to manually wire classes that were designed around the Symfony kernel, its DI extension, and its templating layer. Since the bundle is PHP 5.x-era code, the Composer solver will likely reject it against a modern PHP constraint anyway. Treat any install attempt as a lint-and-audit exercise, not an integration.
- Which Laravel versions support gibilogic/crud-bundle?
- None officially. The package targets Symfony 2, which reached end of life in January 2019, and it has no Laravel service provider, no facade, and no package discovery entry. There is no version of Laravel that can consume a Symfony bundle's DI wiring natively. If you need CRUD scaffolding in Laravel, use a native package or build a resource controller instead.
- Does gibilogic/crud-bundle work on PHP 8.2 or PHP 8.3?
- Assume a PHP 5.x ceiling until proven otherwise. Symfony 2-era code commonly breaks on PHP 8 through dynamic property deprecations, removed functions, and reserved-word collisions. A quick composer require against your PHP constraint plus a parse and lint pass will answer this in minutes. Expect deprecation-level breakage at minimum even where the code parses cleanly.
- Does gibilogic/crud-bundle require Doctrine or Symfony Forms?
- The README does not spell out dependencies, but a Symfony 2 CRUD bundle of this vintage almost certainly leans on Doctrine ORM, Symfony Forms, and the Request/Response stack. Doctrine is reachable in Laravel through laravel-doctrine, but adopting an ORM bridge purely to reuse a two-star helper bundle inverts the cost-benefit calculation. Audit each class for framework coupling before assuming anything is portable. Anything touching the kernel, the DI extension, or Form types should be discarded.
- How do I port a Symfony CRUD bundle to Laravel?
- Vendor or fork the source into packages/ with a PSR-4 autoload entry rather than adding the upstream package to composer.json. Re-express the bindings as a Laravel service provider using explicit constructor injection, and map concepts deliberately: CRUD service to repository or model, Form type to FormRequest, flash and redirect to with('status'), route YAML to Route::resource. Replace Doctrine repository calls with Eloquent scopes or query objects. Only plain, container-agnostic PHP classes survive the extraction, so expect to rewrite more than you keep.
- Is gibilogic/crud-bundle maintained and safe for production?
- It shows two stars and zero dependents, meaning no community validation, no issue history, and no evidence anyone has run it on a modern runtime. The underlying Symfony 2 platform has received no security patches since January 2019. The MIT license and tiny surface area keep the supply-chain blast radius low, but abandonment risk is high. Do not put it on a production dependency path in a Laravel app.
- What is the difference between a Symfony bundle and a Laravel package?
- A Symfony bundle subclasses Bundle, ships a DependencyInjection extension, and registers at the kernel level so its services and configuration are compiled into the container. A Laravel package exposes a service provider and is often auto-discovered through extra.laravel in composer.json. Laravel consumes individual Symfony components such as HttpFoundation, Console, and Finder, but never bundles. That architectural gap is why this package cannot simply be installed and configured in Laravel.
- What are Laravel-native alternatives to gibilogic/crud-bundle?
- Start with a stock resource controller plus a query-object layer for filtering and pagination, which is a few hundred lines your team already knows how to review. For admin panels, Filament or Laravel Nova cover the list, form, and detail views the bundle advertises. Route::resource, FormRequest validation, and Blade or Inertia views replace the bundle's scaffolding directly. These options are maintained, documented, and tested against current Laravel releases.
- How do I test CRUD code extracted from gibilogic/crud-bundle?
- Assume nothing is inherited, because there is no evidence of a test suite to carry over. Write fresh PHPUnit or Pest feature tests around the extracted classes, using factories and a test database to cover create, edit, delete, and listing paths. Add unit tests for any filtering or pagination logic you reimplement as query objects. Run the suite on your target PHP 8.2 or 8.3 runtime to catch the deprecations the original code would have triggered.
Weaver
How can I help you explore Laravel packages today?