Weave Code
Core Laravel Package
streams/core
The core of Streams, a modular Laravel framework for building data-driven applications and CMS-style platforms. Define database-driven streams, fields, and addons, then manage everything through a powerful control panel. Extensible, developer-friendly, and built for rapid development.
A domain-driven, code-configured, flat-file application platform for Laravel.
Frequently asked questions about Core
- What is Streams Core used for in Laravel?
- Streams Core is the foundation of the Streams platform, a Laravel package for building data-driven applications and CMS-style systems. It lets you define streams as database-backed data structures, attach fields through assignments, and manage them with a fluent API. It is an opinionated engine layer rather than a small utility package, so it fits best when configurable data structures are a core product requirement.
- How do I install streams/core in a Laravel application?
- Install the package with Composer using the streams/core package name, then publish its configuration and migrations and register the service provider. After that you define streams and fields programmatically and read or write data through repositories. Core is deliberately incomplete on its own, so verify whether your use case also requires sibling packages such as streams/platform or streams/ui.
- Which Laravel and PHP versions does streams/core support?
- The exact Laravel and PHP constraints are defined in the package composer.json and should be checked before adoption. The project carries framework-drift risk, and its supported window may trail current Laravel LTS releases. Plan to verify resolution against your target runtime and to widen constraints in an internal fork if needed.
- Do I need streams/ui or streams/platform to use streams/core?
- Streams Core provides the engine layer for streams, fields, assignments, repositories, and criteria, while the control panel and UI layers live in sibling repositories such as streams/platform and streams/ui. Simple programmatic use may be possible with core alone, but any real control-panel feature is likely to pull in the wider package family. Treat core-only installation as an engineering spike, not a complete product story.
- How do I define streams, fields, and assignments in Streams Core?
- Streams Core provides a migration-like API for defining streams, fields, and assignments programmatically. Assignments connect fields to streams, giving you a consistent way to model CMS-style content types and data structures. Use the package documentation for exact syntax, and keep stream definitions out of the schema of record for core business entities.
- How do I query streams using repositories and criteria?
- Streams Core uses repository and criteria patterns so query constraints can be composed instead of scattered across controllers. Criteria encapsulate reusable query logic, and repositories provide a consistent boundary for reading and writing stream data. Keep repository interfaces at your application seam so callers do not depend directly on the package internals.
- Can Streams Core coexist with regular Eloquent models?
- Yes, but it should be adopted as an isolated subsystem rather than as a replacement for conventional Eloquent persistence. Keep the rest of the application on standard models and expose the Streams module through repository interfaces at the boundary. Do not let stream definitions become the schema of record for core business entities unless you have accepted the exit cost.
- How should I test a Streams Core integration?
- Start with integration tests against a test database: define one stream with two representative field types, run one criteria-based query, and exercise one write path. Keep assertions at the repository boundary so the implementation can be swapped without rewriting callers. This mirrors the recommended short spike and proves the package boots on a defensible Laravel version before feature work begins.
- Is streams/core safe for commercial use and actively maintained?
- Repository metadata indicates a NOASSERTION license, so commercial use should be treated as a legal gate until the actual license is confirmed and accepted. Adoption signals are thin, with roughly 170 stars and zero dependents, so the default assumption should be effectively unmaintained until a named, responsive maintainer and recent release activity are verified. Plan for an internal fork as the baseline operating model, not as a contingency.
- How does Streams Core compare with Filament, Nova, or hand-rolled CRUD?
- Streams Core is an opinionated platform engine for configurable data structures, not a drop-in admin panel like Filament or Nova. Compare the net saving after accounting for the learning curve, multi-repository dependency graph, and internal fork ownership. For a bounded module, hand-rolled CRUD over Eloquent may carry lower long-term risk, while Streams Core can fit when dynamic stream schemas are the product requirement.
Weaver
How can I help you explore Laravel packages today?