- How do I install regnerisch/laravel-beyond in a Laravel app?
- Install it with Composer using composer require regnerisch/laravel-beyond --dev, since it is developer tooling rather than a runtime dependency. Laravel package auto-discovery registers the service provider, so no manual provider entry is normally needed. You may need to publish stubs or config with vendor:publish before generating classes. Check the package composer.json for the exact PHP and Laravel constraints before installing.
- Which Laravel versions does Laravel Beyond support?
- Version 7.1.0 adds Laravel 12 support and drops Laravel 10, so the 7.x line effectively targets Laravel 11 and 12. If your application is still on Laravel 10, you must stay pinned to the last 7.0.x release or upgrade the framework first. Always verify the illuminate/console and illuminate/support constraints in the package composer.json rather than relying on release notes alone.
- What classes can I generate with Laravel Beyond?
- Laravel Beyond provides Artisan generators and base classes for Actions, Data Transfer Objects, and View Models. The beyond:make:adr-action command scaffolds an action class following the ADR (Action-Domain-Responder) style. These generators help you organize domain logic instead of defaulting to CRUD controllers and models. Generated files are normal PHP classes that you commit to your application source.
- Should laravel-beyond be required as a dev dependency?
- Yes, in most cases. The package registers an Artisan command at the console layer and scaffolds files; it does not intercept routing, persistence, or queue behavior at runtime. Requiring it with --dev keeps it out of production installs. The generated classes themselves are committed to source, so production does not need the package unless you consume something at runtime.
- What does the beyond:make:adr-action command generate?
- It is an Artisan generator that scaffolds an ADR-style action class into your application or domain directory. The output is a PHP stub that you then fill in with your business logic. It is a build-time scaffolding tool, not a runtime action registry. Check the published stubs to see the exact template and namespace conventions used.
- Does Laravel Beyond work with Laravel 10?
- Not on version 7.1.0, which removed Laravel 10 support. Laravel 10 projects should pin explicitly to the last 7.0.x release rather than using a floating ^7.0 constraint that could strand them. Treat that pin as temporary and tie it to your framework upgrade backlog. Once you are on Laravel 11 or 12, bump the package after the framework upgrade.
- How is Laravel Beyond different from Spatie Laravel Beyond CRUD?
- Laravel Beyond is inspired by Spatie's Laravel Beyond CRUD approach and packages those ideas into Artisan generators and base classes. It focuses on scaffolding Actions, DTOs, and View Models so you can structure domain logic outside traditional CRUD. It is a lighter tooling layer rather than a full architectural framework. Evaluate the generated directory structure against your team conventions before adopting it widely.
- Is Laravel Beyond safe to use in production?
- The package operates at the console and kernel layer: a service provider registers an Artisan command that scaffolds files. It does not intercept requests, database access, or queues, so the runtime blast radius is minimal. That makes it a dev-time dependency in practice. The real risks are Composer constraint collisions with other dev tooling and upgrade churn, not production traffic.
- How do I upgrade Laravel Beyond to 7.1.0 without breaking CI?
- Upgrade your Laravel framework to 11 or 12 first, then bump the package, so any Composer resolution failure is clearly attributable. Run composer why-not regnerisch/laravel-beyond 7.1.0 to surface conflicting constraints from static analysis, test generators, or IDE helper packages. Inventory each app and CI image by Laravel major version using composer show laravel/framework. Pin exact versions in CI rather than relying on floating ranges.
- Who maintains Laravel Beyond and how stable is it?
- The package is maintained by a single primary contributor and is already at a v7 major release, which signals both active development and frequent major-version churn. That concentration is a bus-factor and longevity consideration for a tool embedded in your engineering workflow. Pin versions, review release notes for support-matrix changes, and be ready to fork or replace the generators if maintenance stalls. The blast radius is limited to developer tooling and CI.