Weave Code
Armada Laravel Package
armsys-tech/armada
Armada is a Laravel/PHP package from armsys-tech that provides a lightweight, framework-friendly way to add its core functionality to modern PHP applications. It aims for straightforward installation and configuration, making it easy to integrate into Laravel projects.
At a glance
Frequently asked questions about Armada
- How do I install Armada in a Laravel project?
- Install the package with Composer, publish its assets, and then publish only the components you plan to use. Armada is Blade-native and does not add migrations, runtime services, or service providers that mutate application behaviour. You can adopt it incrementally and reverse individual components without a broad rewrite.
- Does Armada support Livewire bindings and validation errors?
- Yes. The form family supports wire:model bindings and automatic validation-error rendering, and the package includes a Livewire toaster API. This is the highest-value integration area, but it is also the highest-blast-radius one. The Livewire version dependency is not stated in the package notes, so pin and test it against your Livewire major before production.
- What Laravel, PHP, and Livewire versions does Armada support?
- Armada v1.0.0 is the first stable release, and the package notes do not state a supported PHP, Laravel, or Livewire matrix, support window, or LTS policy. Check composer.json and CI configuration for enforced version constraints. Treat the Livewire pin as critical because form binding, validation-error rendering, and toaster behaviour can degrade across Livewire majors.
- Do I need Tailwind CSS to use Armada components?
- The package notes do not confirm whether Tailwind is required or which major is supported. Armada delivers design tokens as --arm-* custom properties and uses cascade layers, so application CSS is explicitly ordered to win. Verify in the repository whether tokens ship as prebuilt CSS or are compiled by your host build.
- Will Armada break my existing application's CSS?
- Armada is designed for brownfield adoption: it uses --arm-* design tokens and cascade layers with application CSS ordered last. That materially lowers the risk of visual regressions in an existing product, but you should still audit shipped CSS weight and overrides. Per-component publishing lets you isolate changes to specific components.
- Is Armada accessible and WCAG 2.2 AA compliant?
- The package notes do not include a WCAG 2.2 AA conformance claim or mention automated accessibility testing such as axe in CI. Command palette, combobox, kanban, drawers, date pickers, and toasts are common failure points for keyboard and screen-reader support. Treat accessibility verification as required before enterprise or public-sector use.
- How do I override or customize an Armada component?
- Publish individual components with vendor:publish --tag=armada-components, then edit the published Blade files. This is the intended per-component override primitive, but it creates a local fork by design. Track upstream changes and re-publish deliberately rather than editing vendor files directly.
- What JavaScript does Armada use, and is it CSP-friendly?
- The notes do not specify the JavaScript model per component, whether Alpine directives, Livewire hooks, or standalone modules are used, or the total shipped JS and CSS weight. Command palette, kanban, infinite scroll, drawers, and dropdowns carry the most custom JavaScript risk. The inline no-flash theme script and rich text output also need review against a strict CSP.
- Can Armada charts handle large datasets?
- Armada uses server-rendered SVG charts, which avoids a chart library and client runtime and is privacy-friendly. That trade-off forgoes hover tooltips, zoom, brush, and streaming. For large datasets, use pagination or server-side aggregation to control HTML payload and paint cost.
- Is Armada production-ready, and how is it tested?
- v1.0.0 has no operating history, and shipping more than 100 components in a first stable cut means coverage will likely be uneven. The package notes do not detail the test strategy or coverage. Before production, verify rich text sanitisation, file-upload validation and storage configuration, and the inline no-flash theme script under your CSP.
Weaver
How can I help you explore Laravel packages today?