Weave Code
Ui Laravel Package
streams/ui
UI components and helpers for the Streams platform on Laravel, offering reusable Blade views and front-end building blocks for admin screens and app interfaces. A lightweight way to add consistent Streams styling and UI patterns to PHP/Laravel projects.
The UI package for the Streams platform.
Frequently asked questions about Ui
- What is streams/ui used for in Laravel?
- Streams UI is the presentation and control-panel layer for applications built on the Streams platform. It ships reusable Blade components, layouts, navigation, forms, tables, and styling conventions for admin screens and front-end views. It is not a general-purpose Laravel UI kit and is most useful when Streams is already your application platform.
- Does streams/ui work without streams/core or the Streams platform?
- No. streams/ui expects streams/core and the Streams addon model to be present, so it is a platform component rather than an independent library. In a conventional Laravel, Eloquent, and Blade codebase it introduces a parallel architecture alongside standard MVC. Treat it as part of the Streams baseline, not a standalone package you bolt on.
- How do I install streams/ui with Composer?
- Install and configure the Streams platform first, then require streams/ui with Composer and verify that the control panel boots correctly. Check the package composer.json for exact version constraints against streams/core and sibling addons. Publish or override views and assets only after the platform baseline is working, because version alignment matters more than the install command itself.
- Which Laravel and PHP versions does streams/ui support?
- Support is tied to the Streams platform release you install, so inspect composer.json constraints and the matching streams/core version rather than assuming broad Laravel compatibility. There is no public integration precedent or downstream issue history to confirm tested version combinations. Verify PHP and Laravel support, and check for a CI matrix, before committing to an upgrade path.
- Is streams/ui a good alternative to Filament, Nova, Backpack, or Orchid?
- For a generic Laravel admin panel, no. Filament, Nova, Backpack, and Orchid have far more adoption, documentation, and hiring pool, and choosing streams/ui for admin UI alone is hard to justify on risk grounds. Streams UI makes sense only when you are deliberately building a modular, addon-driven application on the Streams platform.
- Can I customize streams/ui Blade components and layouts for branding?
- Yes. The package provides customizable views, layouts, and UI conventions that can be adapted for project-specific branding. In practice you will publish or override Blade views and learn extension points such as fields, table columns, form controls, and themes from source. Be aware that deep theme and asset-pipeline customization creates lock-in that is expensive to reverse later.
- Is streams/ui production-ready and actively maintained?
- Treat it as high risk until you inspect the repository yourself. It has very low public adoption, no recorded dependents, and single-vendor stewardship, which means limited ecosystem pressure to keep APIs stable. Review commit history, release cadence, test coverage, and CI posture before using it in production, and plan for a possible bus-factor problem.
- Can I use streams/ui in an existing Laravel app alongside normal MVC?
- It is not a drop-in addition to an existing conventional Laravel application. The realistic path is a strangler pattern: stand up Streams alongside your current app, verify coexistence, and migrate administrative surfaces addon by addon. Expect a parallel architecture of streams, fields, assignments, criteria, and repositories while both systems run.
- What asset build pipeline does streams/ui use, Vite or Mix?
- The package includes asset handling as part of the Streams UI layer, but you should verify the exact pipeline in the source and platform documentation rather than assuming Vite or Mix. Confirm how assets are compiled, published, and versioned before integrating. Asset and theme lock-in is a secondary risk, so test the build process early.
- How should I test and upgrade streams/ui in a Laravel project?
- Start by booting the Streams control panel and exercising the Blade components, forms, tables, and navigation your app depends on. Pin streams/ui and streams/core to aligned versions, run those checks in CI, and review semantic-versioning policy and breaking changes before Laravel major upgrades. Because there is no public upgrade path or dependent cohort, budget time for source-level verification.
Weaver
How can I help you explore Laravel packages today?