Weave Code
Pi Crud Laravel Package
pi-web/pi-crud
pi-web/pi-crud is a Laravel package for scaffolding CRUD (create, read, update, delete) functionality, aimed at cutting boilerplate when building data-management screens. An early-stage project with little adoption so far.
At a glance
Frequently asked questions about Pi Crud
- How do I install pi-web/pi-crud in a Laravel application?
- Install it with Composer using composer require pi-web/pi-crud. Laravel's package auto-discovery should register the service provider, so no manual provider entry is normally needed. After installing, publish the package assets so you can adapt the config and views to your project. Confirm the exact package name and requirements in the README and composer.json before adding it to an existing app.
- How do I publish the pi-web/pi-crud config and Blade views?
- The package ships publishable configuration and views, which is the main way you take ownership of the generated scaffolding. Run php artisan vendor:publish and pick the pi-web/pi-crud provider from the list, or pass the provider class directly with the --provider flag. Once published, the files land in your config and resources/views directories where you can edit them freely. Re-publishing later can overwrite your edits, so keep your customizations under version control.
- Which Laravel versions does pi-web/pi-crud support?
- The package description does not pin a specific Laravel release, so check the require block in its composer.json for the framework constraint. Because the project is early-stage, verify compatibility against the Laravel version you actually run rather than assuming support. If you are on an older or brand-new Laravel release, try it in a throwaway branch first. Composer will refuse the install if the constraint does not match, which is a quick way to confirm.
- Does pi-web/pi-crud generate validation rules automatically?
- Yes. Validation rules and request handling are derived from the field definitions in your resource, so you declare each field once and the package wires up the checks. That removes the usual duplication between migrations, form requests, and Blade inputs. You can still override or extend the rules when a field needs custom logic, since the generated code is publishable and editable.
- Can I customize the generated CRUD views and controllers?
- Yes. The Blade forms and tables are publishable, so you can restyle or restructure them to match your existing UI conventions. The package is deliberately designed to stay out of your way, with configuration and generated code meant to be adapted rather than locked down. Treat the published files as your own application code and adjust them as needed.
- Does pi-web/pi-crud include search, filtering, and pagination out of the box?
- The package advertises built-in search, filtering, and pagination for the generated tables. That means index screens for your Eloquent models arrive with basic data-navigation features instead of a bare list. Because it is an early-stage project, test these features against your dataset size and query patterns before relying on them in production.
- Can I use pi-web/pi-crud with existing Eloquent models and database tables?
- The package scaffolds CRUD around Eloquent models, so it is intended to sit on top of models you already have rather than forcing a schema of its own. You define a resource and its fields once, and the package generates the controllers, validation, and views for that model. This makes it a reasonable fit for adding admin screens to an existing Laravel application. Check the README for how field types map to your column types before wiring up complex schemas.
- Is pi-web/pi-crud production-ready?
- It is an early-stage project with limited adoption so far, which means fewer real-world users, fewer bug reports, and a smaller pool of answers online. That does not rule it out, but review the generated code, pin an exact version in composer.json, and cover the critical screens with tests. For sensitive data-management screens, weigh the time saved against the cost of auditing and maintaining the scaffolding yourself.
- How does pi-web/pi-crud compare to Laravel Nova, Filament, or Backpack?
- Nova, Filament, and Backpack are full admin-panel frameworks that render screens from runtime configuration, while pi-web/pi-crud scaffolds plain controllers, requests, and Blade views that become part of your codebase. That makes it lighter and easier to bend to existing conventions, but you get no built-in dashboard, authentication, or ecosystem of add-ons. Choose the scaffolder if you want code you own; choose a panel if you want a batteries-included admin UI.
- How do I test CRUD screens built with pi-web/pi-crud?
- Since the package generates ordinary Laravel controllers and Blade views, your normal HTTP feature tests apply: assert that index, create, store, edit, update, and destroy routes return the expected responses and persist the expected data. Use RefreshDatabase with factories for your models, and assert validation errors for required fields defined in the resource. Testing the generated screens directly also protects you when you customize the published views or upgrade the package.
Weaver
How can I help you explore Laravel packages today?