- How do I install Laravel AutoBuilder in a Laravel app?
- Install it with Composer using composer require grazulex/laravel-autobuilder. Before running the command, check the PHP constraint in the package's composer.json: v1.4.0 requires PHP 8.4 or newer. If your application runs PHP 8.3, pin to the 1.3 release line so Composer resolves deterministically.
- Does Laravel AutoBuilder support PHP 8.3?
- No, v1.4.0 requires PHP >= 8.4. Applications, queue workers, and CI runners on PHP 8.3 or earlier cannot install that version and will resolve to v1.3.x or fail depending on your constraint. Pin explicitly to ~1.3 if you cannot upgrade the runtime yet.
- Which Laravel versions are compatible with Laravel AutoBuilder?
- The v1.4.0 release notes do not change the package API; the governing compatibility constraint is PHP >= 8.4. Confirm that your Laravel version officially supports PHP 8.4 before upgrading, because an upstream Laravel constraint can block the runtime move. Also check the illuminate/support constraint in the package's composer.json for the exact supported range.
- What does Laravel AutoBuilder generate for a Laravel project?
- It automates CRUD scaffolding from your database schema or Eloquent models. That includes generating controllers, routes, forms, and views, which is aimed at speeding up admin panels and internal tools. The package also describes a drag-and-drop visual builder interface.
- Is Laravel AutoBuilder a workflow automation tool or a CRUD scaffolder?
- The package is described as a visual automation builder with a drag-and-drop interface, and its stated purpose is automating CRUD scaffolding from database schemas or Eloquent models. In practice, treat it as a scaffolding and admin-panel accelerator that generates controllers, routes, forms, and views. Confirm the exact workflow-automation scope in the package documentation before committing to it.
- Will upgrading to Laravel AutoBuilder v1.4.0 break my application?
- The release is intended to be behaviour-neutral: it uses Rector-driven modernisation and dead-code removal with no API change, deprecation, or schema/config migration. The breaking change is the PHP runtime requirement, not the package code. Test on PHP 8.4 in a non-production environment before promoting.
- Why did composer update install an older version of Laravel AutoBuilder?
- Because v1.4.0 requires PHP >= 8.4, a host on PHP 8.3 will cause Composer to resolve to v1.3.x silently. That creates feature drift without an obvious failure signal. Pin the dependency explicitly to the release line you intend to run so resolution is deterministic.
- How should I plan the PHP 8.4 upgrade for Laravel AutoBuilder?
- Treat v1.4.0 as a runtime upgrade project with a package bump attached. Inventory consumers and version constraints, upgrade PHP to 8.4 in a non-production environment, then upgrade the package and run your full test suite plus integration tests. Promote to staging and then production, and avoid combining it with a Laravel major-version upgrade.
- What are the risks of upgrading Laravel AutoBuilder in a large codebase?
- The main risks are constraint resolution and transitive dependencies, not the package's own logic. Other dependencies that lag on PHP 8.4 support can make the upgrade infeasible even when your application is ready. Docker base images and extension chains also need verification before the jump.
- Is Laravel AutoBuilder actively maintained and production-ready?
- The package tracks the PHP release cadence closely: CI covers PHP 8.4 and 8.5, and the Docker image is rebased on 8.4. That is a good longevity and security signal, but it means the package will consistently lead your runtime by one major version, so plan for a recurring annual upgrade. It is suitable for admin panels and internal tools, but evaluate your own production requirements and dependency graph.