- What is sixlive/laravel-preset and what does it do?
- sixlive/laravel-preset is an opinionated Laravel application preset package that bundles common new-project setup tasks such as installing packages, applying configuration, and generating scaffolding into a single repeatable command. It is a developer-experience accelerator for greenfield projects, not a runtime library. The idea is that every new Laravel app from your team starts from the same conventions instead of a vanilla skeleton.
- How do I install sixlive/laravel-preset with Composer?
- You install it as a dev dependency with composer require --dev sixlive/laravel-preset, then run the preset command documented in the repository. Because the package was last released in 2019, you should run the install in a disposable sandbox app pinned to your exact Laravel and PHP versions first. Inspect the full diff of generated and modified files before applying anything to a real project.
- Which Laravel and PHP versions does sixlive/laravel-preset support?
- The last release was in March 2019, which predates Laravel 6, so its Composer constraints realistically target Laravel 5.x-era applications and older PHP versions. There is no documented supported matrix for modern Laravel releases. Always confirm compatibility by attempting a sandbox install against your target Laravel and PHP versions, since Composer resolution may simply fail.
- Does sixlive/laravel-preset work with Laravel 10 or Laravel 11?
- It is unlikely to work out of the box on Laravel 10 or 11 because the package predates Laravel 6 and the major changes to frontend and auth scaffolding that followed. Laravel also removed the built-in artisan preset command that era of tooling relied on. Treat it as a reference implementation for older projects, or fork and adapt it if the conventions are still valuable to your team.
- What files does sixlive/laravel-preset create, overwrite, or delete?
- The package generates and modifies application scaffolding files, but the repository does not publish an exhaustive manifest, so you need to determine this empirically. Run the preset command on a throwaway branch or new repository and capture the complete diff. That inventory is essential because preset tooling can overwrite existing configuration, frontend assets, and Composer or npm dependency files.
- Can I use sixlive/laravel-preset in an existing Laravel application?
- You should not retrofit this preset into an existing application, since it is designed for greenfield scaffolding and can destructively overwrite files. The safer approach is to generate a fresh app in a throwaway branch, review what the preset produces, and manually port only the conventions you actually want. Existing projects have too much accumulated configuration for a preset diff to be safe.
- Is sixlive/laravel-preset a production dependency?
- No. This is a scaffolding and developer-experience package, so it belongs in require-dev at most and should never end up in your production dependency graph or as a platform-level architectural component. Once a project is generated, the preset has done its job and can be removed. Treating it as a maintained runtime dependency adds risk with no runtime benefit.
- Does sixlive/laravel-preset depend on Laravel's removed artisan preset command?
- It is likely, because the package was released in early 2019 and Laravel later removed the built-in preset command along with its frontend scaffolding workflow. If the preset command no longer exists in your target Laravel version, the package becomes a reference implementation rather than an installable dependency. Verify this in a sandbox before planning any adoption.
- What are alternatives to sixlive/laravel-preset for Laravel starter kits?
- The most reliable alternatives are the official Laravel starter kits and skeleton, or an internal Composer starter package you own and version yourself. If Sixlive's opinionated conventions are what you want, fork the MIT-licensed repository and maintain it as an internal template. That gives you control over the Laravel and PHP support matrix and dependency freshness.
- Is sixlive/laravel-preset still maintained, and what if it is abandoned?
- The last release was 2019-03-07 and the star count is low, so assume community-only support with no active release cadence or vendor SLA. The MIT license is favorable because it lets you fork and adapt the code, but forking shifts maintenance and security patching to your team. If you adopt it, pin your fork internally, add CI checks, document the supported Laravel and PHP versions, and keep the original package off your critical path.