Weave Code
Laravel Beyond Laravel Package
akrillia/laravel-beyond
Akrillia's Laravel Beyond is a Laravel architecture toolkit that helps you move beyond basic CRUD. It offers conventions and helpers for organizing domain logic, keeping controllers thin, and building maintainable, testable applications that integrate smoothly with existing Laravel projects.
Create Laravel classes in a domain driven way (insired by Spatie Laravel Beyond CRUD)
Frequently asked questions about Laravel Beyond
- What is akrillia/laravel-beyond and what problem does it solve?
- It is a Laravel architecture toolkit for the Action–Domain–Responder pattern, inspired by Spatie's Laravel Beyond CRUD. It provides conventions and Artisan generators so domain logic lives in dedicated action classes instead of bloated controllers. The package layers on top of standard Laravel routing, the container, and the HTTP kernel rather than replacing framework primitives. That makes it a tooling and conventions layer, not a runtime dependency.
- How do I install laravel-beyond in a Laravel application?
- Install it with Composer using composer require akrillia/laravel-beyond, and the service provider is auto-discovered. There are no migrations, queues, cache drivers, or external services implied by the package, so setup is essentially just the dependency plus your team's naming and namespace conventions. Choose a constraint that matches your framework version before running the generator.
- Which Laravel and PHP versions does laravel-beyond support?
- Version 7.1.0 supports Laravel 11.x and 12.x, which implies PHP 8.2 or newer as the floor. Laravel 10.x was removed from the support matrix in that release. Confirm the exact illuminate/* constraints and PHP floor in the package's composer.json, especially if you maintain applications across multiple framework majors.
- Can I use laravel-beyond on a Laravel 10 application?
- Not at 7.1.0, because Laravel 10 support was dropped in that release. You have two realistic options: pin the dependency at ^7.0 and accept a frozen line that stops receiving fixes, or defer adoption until your Laravel 11 upgrade is complete. Do not hold a ^7.1 constraint on Laravel 10, since Composer will hard-fail resolution.
- What does the beyond:make:adr-action command generate?
- It is the generator added in 7.1.0 that scaffolds a new action class into your application following the package's ADR conventions. The command is additive and opt-in, so nothing changes in your codebase until you explicitly run it. It is the main new tooling surface of the release and carries low risk compared with framework-level changes.
- Does the beyond:make:adr-action generator overwrite existing files?
- Overwrite behavior is not spelled out in the release notes, and generators can collide with existing files or previously published stubs. Test the command on a scratch branch first and observe whether it prompts, fails closed, or replaces the file. Confirm the behavior before wiring it into scripts or CI automation.
- Does laravel-beyond change how requests are handled in production?
- No. The package does not introduce a runtime layer or replace routing, the container, or the HTTP kernel; its observable surface is developer tooling and conventions. Actions are ordinary classes resolved through Laravel's container. The practical blast radius of a bad release is broken Composer resolution or stale generators, not user-facing outages.
- Will upgrading laravel-beyond update the code I already generated?
- No. Artisan generators copy stubs at generation time, so upgrading the package leaves existing actions untouched. Stub improvements and convention changes only reach new files unless you deliberately publish the stubs and diff them. In long-lived codebases you should expect generated code to drift from the package version that produced it.
- How do I test actions created with laravel-beyond?
- Actions are plain PHP classes, so you can instantiate them directly in unit tests and pass in dependencies or mocks. For anything that touches HTTP, cover the thin controller with a feature test and keep assertions on the action's outcome. Because the package adds no runtime layer, standard Laravel testing practices apply without special configuration.
- How actively is laravel-beyond maintained, and how often does it drop Laravel majors?
- Release 7.1.0 added Laravel 12 and removed Laravel 10 in the same version, which shows the package tracks Laravel's annual major cycle. Treat that as a predictable breaking change and budget roughly one forced dependency event per year, correlated with your framework upgrade. Check that the CI matrix is green across Laravel 11 and 12 and the supported PHP versions before adopting, and note that dropping a framework major in a minor release is standard ecosystem practice but formally a breaking change.
Weaver
How can I help you explore Laravel packages today?