Weave Code
Facile Laravel Package
orchestra/facile
Facile is an Orchestra Platform package that speeds up Laravel development by scaffolding CRUD resources—models, migrations, controllers, and views—from simple definitions, so you can build admin interfaces and backend modules quickly with less boilerplate.
Orchestra Facile is a lightweight Laravel package that trims boilerplate from everyday application tasks by wrapping common patterns behind a concise, expressive API. It plugs into Laravel's service container and package auto-discovery, so it can be added to an existing project without restructuring your code.
- Expressive helpers that keep call sites short and readable
- Zero-config setup through Laravel package auto-discovery
- Framework-native design that respects existing conventions
- Publishable configuration for sensible, overridable defaults
- Modern PHP codebase built for current Laravel releases
Frequently asked questions about Facile
- What is orchestra/facile and what does it actually do?
- Facile is an Orchestra Platform package that adds a fluent form builder and expressive helpers on top of Laravel, composing field definitions, labels, selects, buttons, old-input and validation-error wiring, and Blade-friendly rendering. Its documentation also describes scaffolding CRUD resources such as models, migrations, controllers and views from simple definitions. Architecturally it is a thin ergonomics layer, so its value depends on the host application already being Orchestra-bootstrapped.
- Does orchestra/facile work on vanilla Laravel or does it require Orchestra Platform?
- It is designed for applications already running Orchestra Foundation, and it assumes that platform's provider ordering and binding set. On a plain Laravel app you mostly add a dependency edge and a set of global symbols in exchange for markup helpers your team could own outright. Treat adoption as a platform-ergonomics decision rather than a product-capability one.
- Which Laravel versions does orchestra/facile support?
- The only release note in public evidence is v6.0.0, which states update support for Laravel Framework v8, a release line that is out of security support. There is no public evidence that the package resolves against a currently supported Laravel release. Confirm the declared illuminate/* and PHP ranges with composer show, composer why-not and a dry-run require before planning any work.
- How do I install orchestra/facile in a Laravel project?
- Install it with composer require orchestra/facile and rely on package auto-discovery to register the service provider, so no manual provider entry is needed. Publish the configuration if you need to override the defaults. Before installing, run a dry-run require and composer why-not to prove a satisfiable constraint set exists for your target Laravel version, because a forced upgrade or downgrade on the main branch should end the evaluation immediately.
- Is orchestra/facile safe to run in production?
- The public signals are thin: zero stars, zero dependents, a composite score of 0.3 and a release line that appears frozen. The main risks are constraint drift across the Orchestra family, boot-order failures that surface as missing methods at render time, and silent behavioural drift in old-input handling or escaping inside forms nobody tests. The quiet drift path is the expensive one, so mitigation is mandatory rather than optional.
- How should I test forms built with orchestra/facile?
- Add a boot smoke test to CI so provider ordering problems fail at boot rather than at render time. Write view or snapshot tests that assert specific input names, labels and selected options, plus an escaped-path test that pushes quotes and angle brackets through every field type you use. Wrap every call site in an application-owned adapter so the package name appears in exactly one directory.
- What are the alternatives to orchestra/facile for building Laravel forms?
- Native Blade components, hand-rolled partials, or a full admin framework such as Filament, Orchid or Nova all cover the same ground without an Orchestra dependency. A small internal form helper is often the cheapest option for a dozen consistent CRUD screens. Measure the package's public API by reflection first, because if it exposes fewer than roughly ten symbols, reimplementation is an afternoon of work.
- Is orchestra/facile worth keeping if we could rewrite it ourselves?
- Use reflection to count the public API surface before deciding. If it is under roughly ten symbols, reimplementation is cheap and the dependency is hard to justify, particularly for internal back-office tooling that never touches revenue. The dependency only makes sense when the app is already committed to Orchestra and the saved glue code is genuinely repetitive.
- How do I publish and override the orchestra/facile configuration?
- The package ships publishable configuration with sensible defaults you can override through Laravel's vendor:publish command. Because Orchestra packages assume a specific provider order and binding set, any macros, field types or view overrides must attach in a provider declared after the package's own provider. Ordering bugs typically appear as missing methods at render time rather than as boot errors.
- Who maintains orchestra/facile and what happens at the next Laravel major?
- Public evidence shows no named maintainer activity, zero dependents and a release line last aligned to Laravel 8. Orchestra components move in lockstep, so adopting one component drags in the maintenance posture of the whole family, and partial upgrades are the primary breakage vector. Assign a named owner who will carry the adapter through the next Laravel major before you adopt it, and keep every target surface off the customer-facing and revenue-critical path.
Weaver
How can I help you explore Laravel packages today?