Weave Code
Laravel Flora Laravel Package
qruto/laravel-flora
A lightweight Laravel package that adds expressive filtering, sorting, and searching to Eloquent queries. Flora helps you build clean, maintainable API endpoints and data tables with minimal code, keeping controllers and models simple and readable.
Install and update Laravel application with single command
Frequently asked questions about Laravel Flora
- What is qruto/laravel-flora used for?
- It is a Laravel developer tool that installs and updates a curated set of Composer packages through an artisan command, aimed at greenfield projects and standardizing a team package set. The technical evaluation describes it as a scaffolding tool invoked outside the request lifecycle, not a runtime library. Review the resulting composer.json diff before committing.
- How do I install qruto/laravel-flora in a Laravel project?
- Add it as a dev dependency with Composer, then run its artisan install command on a clean branch or disposable spike repository. The evaluation recommends capturing the full Composer diff and any published config before accepting changes. Do not run it in a pipeline that auto-commits.
- Is qruto/laravel-flora a runtime package or a dev dependency?
- It is a dev-only scaffolding and installer tool invoked via artisan, so it sits outside the request lifecycle and has effectively zero runtime blast radius. Its durable effects are Composer file mutations and any published config. Keep it out of production images and deploy pipelines.
- Which Laravel and PHP versions does qruto/laravel-flora support?
- The provided evaluation does not include an exact Laravel and PHP support matrix, so check the package composer.json constraints and any CI matrix before adopting. Because Laravel ships annual majors, re-check compatibility against each new Laravel major. Pin an exact version in require-dev with a committed lock file.
- Does laravel-flora add filtering, sorting, and searching to Eloquent queries?
- Based on the technical evaluation and package overview, laravel-flora is an installer, updater, and scaffolding tool, not a runtime Eloquent filtering or sorting library. The filtering, sorting, and searching blurb appears inconsistent with the command-based behavior described. For query filtering, evaluate a dedicated runtime package instead.
- What is in the default package set and can I customize it?
- The evaluation says the tool pulls in a curated set of third-party packages chosen by the maintainer, but it does not list the exact set. Treat every run as expanding your dependency surface and review the composer.json diff as a required gate. Check whether the package offers config or flags for customization and version pinning before relying on defaults.
- Can I run laravel-flora non-interactively in CI or containers?
- The tool is described as interactive and shells out to Composer, so a genuinely non-interactive mode needs verification via flags or --no-interaction. Even if it runs in CI, avoid auto-committing its Composer mutations. Use a throwaway branch or container with registry access and a clean git tree.
- What does flora:update do and is there a dry-run or diff preview?
- The evaluation flags this as a key question: confirm whether flora:update performs a scoped update or a broad composer update. It also asks whether a dry-run or diff preview exists. Until verified, run it only on a disposable branch and inspect composer.json and composer.lock changes before merging.
- Does laravel-flora modify files beyond composer.json and composer.lock?
- The evaluation identifies Composer file mutations and any published config as the main durable artifacts, and it asks whether .env, config, or service providers are also changed. Verify reversibility on a clean git tree before using it on a real project. If it mutates non-Composer files, review and commit those changes separately.
- Is qruto/laravel-flora safe for existing Laravel apps or production?
- The evaluation recommends skipping installation on mature or active applications and using the repository only as a reference catalog of package picks. For greenfield projects, spike it on a disposable branch, capture the full delta, and bake the accepted post-Flora state into your starter template. It is not intended for production images or deploy pipelines, and removal cost is low because you can delete the dev dependency and keep the packages.
Weaver
How can I help you explore Laravel packages today?