Weave Code
Support Facades Laravel Package
orchestra/support-facades
A Laravel package that provides facades for Orchestra Support, offering clean static access to shared support services and helpers. It helps Orchestra Platform applications use familiar facade syntax while keeping code expressive and dependencies organized.
Support (Facades) Component for Orchestra Platform
Frequently asked questions about Support Facades
- What is orchestra/support-facades used for?
- It provides Laravel facades that expose Orchestra Support utilities through a static API, mainly for helpers such as formatting, memory, and string handling. It is intended for Orchestra Platform components and packages that want a consistent facade syntax across their codebase. In a plain Laravel application, constructor injection is usually a better default.
- How do I install orchestra/support-facades in Laravel?
- Install it with Composer using composer require orchestra/support-facades, then follow the README to register the service provider and any facade aliases your application uses. The package uses PSR-4 autoloading and v7 is designed for Laravel 9+ and PHP 8.1+. Do not treat the Laravel 9 floor as a support guarantee; verify that your Laravel version is still receiving security support.
- Does orchestra/support-facades support Laravel 10, 11, or 12?
- v7 requires Laravel 9 or higher, so newer major versions fall within the stated floor, but the real supported matrix depends on the package's CI coverage and release notes. Check the repository for tested Laravel and PHP combinations before upgrading a production application. The technical assessment also flags that Laravel 9 itself is already past security support.
- Is orchestra/support-facades a good fit for a normal Laravel application?
- Usually no. It is most useful inside an Orchestra Platform estate where multiple orchestra/* packages share facade bases and aliases, while conventional Laravel applications generally favor constructor injection and container resolution. If you only need a few static helpers, a small internal adapter is often simpler and avoids a permanent dependency.
- What helpers can I access through the Orchestra Support facades?
- The package exposes facade accessors for Orchestra's support utilities, including formatting, memory, and string handling helpers as described in the overview. The exact facade names and method signatures should be taken from the package source and README for your installed version. Do not assume all Orchestra Support helpers are covered by every release.
- How do I test code that uses orchestra/support-facades?
- Because the package is facade-based, tests should clear or mock the underlying container bindings rather than relying on global static state. In Laravel, facade fake and swap patterns can help, but verify that the specific Orchestra facade bases support the swapping behavior you need. For new code, injecting the underlying service is easier to test than calling facades directly.
- What are the alternatives to orchestra/support-facades?
- For a plain Laravel application, use constructor injection, the container, or a small internal facade or adapter class instead of adding this package. Inside Orchestra Platform, the main alternative is often to stay version-lockstep with the other orchestra/* packages rather than replace one piece. Writing a roughly 50-line internal base class is a realistic build-vs-buy option for simple static access.
- Is orchestra/support-facades actively maintained?
- The assessment notes weak adoption signals: zero dependents and negligible traction, which suggests maintainer-internal ecosystem tooling rather than a broad community package. Continuity depends on one maintainer and the Orchestra organisation's continued investment. Register it as a governance and supply-chain risk, and check release cadence and security disclosure before adopting.
- Does v7.0.0 of orchestra/support-facades have breaking changes?
- v7.0.0 raises the framework floor to Laravel 9 and may legitimately change facade base classes, alias resolution, or accessor behavior beyond the documented constraint bump. Review the changelog and any v6-to-v7 migration guide before upgrading. Facade changes can break at runtime rather than at Composer install time.
- Can I use orchestra/support-facades in production?
- It can be used in production in an Orchestra Platform context where the dependency is already implied and version-locked with other orchestra/* packages. For other applications, the production concern is the recurring cost: upgrade work per Laravel major, security review per release, and a named dependency owner. Confirm the supported Laravel and PHP matrix, maintenance status, licence, and supply-chain clearance first.
Weaver
How can I help you explore Laravel packages today?