Weave Code
Core Laravel Package
lara-zeus/core
Lara Zeus Core is the shared foundation behind the Lara Zeus package family, providing common helpers, base classes, and utilities that power its forms, tables, and admin tools. Install it as the supporting dependency for a consistent, lightweight Laravel experience.
lara-zeus/core is the foundation package for the Lara Zeus ecosystem—a suite of Laravel packages for rapidly building admin panels and dynamic UIs. It bundles the shared helpers, base classes, and configuration that other Zeus packages (such as forms, tables, and bolts) depend on, keeping your stack consistent and lightweight.
- Central place for shared Zeus helpers and utilities
- Base classes and contracts powering other Lara Zeus packages
- Publishable configuration for consistent setup
- Seamless integration with Laravel and Filament
- Actively maintained within the growing Zeus ecosystem
Frequently asked questions about Core
- What is lara-zeus/core and do I need to install it directly?
- It is the foundation package of the Lara Zeus ecosystem, bundling shared helpers, base classes, contracts, and publishable configuration that sibling packages such as forms, tables, and bolts depend on. In most cases you should not require it directly: it arrives transitively when you install a Zeus capability package. Adding it as a direct dependency is only justified when you subclass its base classes, implement its contracts, or override its views.
- How do I install lara-zeus/core with Composer?
- Run composer require lara-zeus/core if you genuinely need it as a direct requirement, then publish any configuration you intend to change using vendor:publish with the package's tag. The recommended path is to install one sibling capability package instead, which pulls core in automatically and keeps your composer.json honest about intent. Always clear and rebuild the config cache after publishing so changes are not masked by a stale cache.
- Which Laravel, Livewire and PHP versions does lara-zeus/core support?
- Core sits inside the Lara Zeus family, so its constraints track the sibling packages you pair it with, and version lockstep across the family is common. Check the composer.json constraints on the repository and Packagist rather than assuming, because narrow constraints are the usual reason a security patch becomes hard to apply. Verify the Laravel, Livewire, PHP, and Tailwind/Vite matrix in an actual build, not on paper.
- Do I need Filament and Livewire to use lara-zeus/core?
- Yes for practical purposes: the Lara Zeus ecosystem targets Laravel with Filament, Livewire, and a Tailwind/Vite asset pipeline. Core itself is a convention layer with no user-facing features, so it is meaningless without a capability package built on that stack. If your admin pain is unique domain logic rather than repetitive CRUD scaffolding, this is the wrong tool and the evaluation should stop.
- Is lara-zeus/core useful on its own without other Zeus packages?
- No. Installed alone it produces an installed package and effectively nothing observable, so there is no standalone return on investment to evaluate. Adopt at least one named sibling capability first and let core come along transitively. If no sibling package is funded or justified, there is no decision to make about core.
- How do I publish and override the lara-zeus/core configuration?
- Use Laravel's vendor:publish command with the package's config tag, and prefer scoped tag-based publishing so you only copy the files you actually intend to override. Core registers convention-based config keys that sibling packages resolve against, so changing them affects the whole family. The published config and the service provider are effectively the specification, since the documentation is thin.
- Why are my Lara Zeus styles or scripts missing in the production build?
- Core ships CSS and JavaScript that assumes your Tailwind content globs reach into vendor/lara-zeus directories. A common failure is styles rendering in npm run dev but disappearing in npm run build because the globs do not cover the vendor paths. Add the vendor globs to your Tailwind config and confirm the compiled output before shipping.
- How should I test a lara-zeus/core integration in a Laravel app?
- Confine every LaraZeus import behind a single adapter or bridge file so domain code never touches Zeus types, then smoke test config caching, asset compilation, and the sibling package's core screens. Keep the exposure internal to dashboards or back-office flows, where a break is an inconvenience rather than an outage. Feature tests around your adapter boundary give you the most value for the least coupling.
- What are the production risks of depending on lara-zeus/core?
- The realistic failure modes are pollution and drift rather than crashes: global helper or Blade directive name collisions, stale config cache masking changes, Tailwind globs that break only in production builds, and lockstep version bumps across the Zeus family that can force a Laravel or Livewire upgrade. Bus factor is roughly one, with no support contract, SLA, or published security disclosure process. Decide in advance whether your response to an unpatched blocker is patch-and-wait or fork.
- How is lara-zeus/core maintained and what are the alternatives?
- It is actively maintained as part of the growing Lara Zeus ecosystem, but with a single primary maintainer and little recorded dependent evidence, so you will be discovering edge cases yourself. Alternatives include building your own Filament scaffolding, adopting individual Filament plugins, or choosing a more established admin panel package. If you stay, record a quarterly dependency-review owner and a clear exit trigger for the containment boundary.
Weaver
How can I help you explore Laravel packages today?