Weave Code
Crudit Bundle Laravel Package
2lenet/crudit-bundle
CruditBundle is a Symfony bundle for building admin CRUD interfaces fast. It offers configurable list, show, edit, and create views with pagination, sorting, filters, batch actions, CSV/Excel export, maps, workflows, and a ready-made SB Admin layout.
The easy like Crud'it Bundle.
Frequently asked questions about Crudit Bundle
- Is 2lenet/crudit-bundle a Laravel package?
- No. CruditBundle is a Symfony bundle, not a Laravel package, despite being installable through Composer. It depends on Symfony controllers, Twig, Symfony Forms, Doctrine-oriented datasources, Symfony Security, and Webpack Encore. For a Laravel application, evaluate Laravel-native admin tools such as Filament, Nova, or Backpack, or run a separate Symfony admin service.
- How do I install CruditBundle in a Symfony application?
- Install it with Composer using 2lenet/crudit-bundle, then add frontend dependencies such as bootstrap@5, sass, sass-loader, @fortawesome/fontawesome-free, and easymde via npm. Configure Webpack Encore, extend the Crudit SB Admin layout in your base Twig template, and import the Crudit SCSS after your own SCSS imports. The application also needs Symfony Security configured before the admin views are usable.
- What Symfony, PHP, Doctrine, and frontend versions does CruditBundle require?
- The README excerpt does not publish a complete compatibility matrix, so check the package composer.json, release notes, and CI badges before committing. The bundle assumes a Symfony application using Doctrine, Twig, Symfony Security, Webpack Encore, Bootstrap 5, Sass, FontAwesome, and EasyMDE. Pin Symfony, PHP, Doctrine, Bootstrap, and phpspreadsheet versions and validate the Encore build in CI because compatibility drift is a real risk.
- What CRUD views and admin features does CruditBundle provide?
- CruditBundle provides configurable list, show, edit, and create views for Symfony admin interfaces. Built-in features include pagination, sorting, filters, item and list actions, batch actions, CSV and Excel export, list grouping, maps, workflows, sublists, and an SB Admin layout. It is designed around a CRUD config class, an independent controller, a datasource, and an optional filterset.
- Can I use CruditBundle without Doctrine?
- CruditBundle is Doctrine-first in practice, and the documented architecture includes a datasource abstraction plus an optional filterset. A custom datasource may be technically possible, but the excerpt does not establish that non-Doctrine datasources are production-ready for complex entities. Pilot a custom datasource against real requirements before relying on it for a non-Doctrine datastore.
- How customizable are CruditBundle list, show, and form views?
- CruditBundle uses Twig templates, Symfony Forms, bricks, menus, brands, filters, form types, and Twig extensions, so customization is possible within its Symfony and Bootstrap 5 conventions. The documentation excerpt notes TODOs for layout and block customization and incomplete design principles, so budget time for template, SCSS, and Encore work. Start with one entity and verify the layout, form types, filters, and permission model before expanding.
- What security concerns should I review before using CruditBundle?
- Review the security model for field-level permissions, row-level access, batch actions, exports, and markdown content because the excerpt does not fully document these areas. Use Symfony Security voters and access control deliberately, restrict who can run batch actions and exports, and sanitize or validate markdown and exported data. Treat CSV and Excel export handling as a data exposure risk, not just a convenience feature.
- How do I test an application that uses CruditBundle?
- The README includes a Test your application recipe, so use Symfony functional tests around list, show, create, edit, filters, batch actions, and exports. Verify the Webpack Encore build, SCSS import order, and Twig layout rendering in CI because frontend build coupling is a known integration constraint. Pin dependencies and test against the Symfony, PHP, Doctrine, and Bootstrap versions you plan to support.
- Is CruditBundle actively maintained and safe for production?
- CruditBundle shows active 1.17 to 1.20 patch and minor releases, which is positive for responsiveness. However, it has low public adoption, no evident dependents, and a single-vendor maintenance model, so production risk is higher than mainstream admin frameworks. Use a bounded pilot, read release notes for minor upgrades, and plan who owns upgrades or a fork if vendor support slows down.
- What are Laravel alternatives to CruditBundle for admin CRUD?
- For Laravel applications, evaluate Laravel-native options such as Filament, Nova, or Backpack instead of directly integrating CruditBundle. CruditBundle is Symfony-native and expects Symfony, Twig, Doctrine, Security, and Encore conventions. If you need this bundle specifically, run it as a separate Symfony admin service rather than treating it as a drop-in Laravel package.
Weaver
How can I help you explore Laravel packages today?