Weave Code
Resources Laravel Package
kraenzle-ritter/resources
A Laravel package for working with application resources, offering a structured way to define, organize, and manage resource classes so resource-related logic stays consistent and reusable across your projects.
Laravel package for managing external resources with Livewire components
Frequently asked questions about Resources
- How do I install kraenzle-ritter/resources in a Laravel app?
- Install it with Composer using composer require kraenzle-ritter/resources. The package is described as zero configuration, so after installation you can start defining resource classes immediately. Confirm the required Laravel, PHP, and Livewire versions in the package's composer.json before adding it to an existing application.
- What Laravel and PHP versions does kraenzle-ritter/resources support?
- The provided material does not publish a minimum Laravel or PHP version matrix. The v3.0.0 release note only states an upgrade to Livewire 4, so you should check composer.json and Packagist for the exact constraints. For production, verify that your host application's Laravel and PHP versions satisfy those constraints before upgrading.
- Does kraenzle-ritter/resources require Livewire 4?
- The v3.0.0 release note reads Upgrade to Livewire 4, which indicates that version 3 of the package tracks Livewire 4. The TPM assessment treats Livewire as a hard runtime dependency and expects the package to share a stateful boundary with Livewire's component lifecycle. If your application or another package is pinned to Livewire 3, treat that as a Composer dependency conflict and resolve it before adopting v3. Check the release notes and composer.json for the exact supported range.
- How do I define a resource with model, controller, policy, routes, and views in one class?
- You create a small, fluent resource class that declares the model, controller, policy, routes, and views for one application resource. That class becomes the single source of truth for routing, authorization, and serialization, so you do not repeat the same wiring across multiple files. The package is convention-first and works with standard Laravel models, controllers, and policies.
- Can I override the default routing, authorization, or serialization behavior?
- Yes. The package is described as having overridable hooks with sensible defaults and escape hatches for custom behavior. You can keep the convention-based routing, authorization, and serialization for most resources and override only the parts that need custom logic. Confirm the exact hook names and method signatures in the package source or documentation because the README excerpt is not included here.
- How do I register resources individually or in bulk?
- You can register resources individually or in bulk, according to the package overview. This lets you keep explicit registrations for a small application and switch to bulk registration as the number of resources grows. Registration is where the resource definitions become available to routing, authorization, and serialization.
- Is kraenzle-ritter/resources suitable for production use?
- It can be suitable for production if your dependency graph matches the package's constraints, especially the Livewire 4requirement reported for v3.0.0. The TPM assessment rates technical risk as medium-high because the release note is thin and does not document the full API changes, support window, or migration guide. Before production use, run your test suite, smoke-test the rendered surfaces, and confirm that no other Composer package blocks the required Livewire version.
- How do I test resources defined with kraenzle-ritter/resources?
- Test your resource definitions the same way you test the underlying Laravel routes, controllers, policies, and views. Use feature tests to assert route registration, authorization outcomes, and serialization responses, and use the package's overridable hooks to substitute fakes where needed. Because v3.0.0 is tied to Livewire 4, include a smoke pass over any Livewire-rendered surfaces in your test matrix.
- What are alternatives to kraenzle-ritter/resources for organizing Laravel resources?
- Alternatives include plain Laravel resource controllers and route model binding, Laravel's policy and authorization conventions, and your own base resource class or service provider registration. The package's differentiator is a single fluent definition that covers model, controller, policy, routes, and views, rather than a new framework layer. If you already have a consistent internal convention, compare the maintenance cost of that convention with adopting an external package that tracks Livewire major versions.
- How is kraenzle-ritter/resources maintained and what is the upgrade path from v2 to v3?
- The provided material shows a v3.0.0 release that upgrades to Livewire 4, but it does not state whether v2 remains supported or for how long. Treat v2 to v3 as a dependency-graph migration: map every Composer package that declares livewire/livewire, identify anything pinned to Livewire 3, and spike the upgrade on an isolated branch. Ask the maintainer for an upgrade guide, the test matrix, and the support window before committing to v3 in production.
Weaver
How can I help you explore Laravel packages today?