Weave Code
Artemis Laravel Package
lara-zeus/artemis
Artemis is a Laravel package from LaraZeus that adds its functionality to Laravel applications. It is intended for developers working in the Laravel ecosystem and is installed via Composer. See the package README for setup, configuration, and usage details before integrating it into your project.
Artemis is a Laravel package from the Lara Zeus ecosystem, designed to drop into existing Zeus-powered applications with minimal setup. It follows standard Laravel conventions—service providers, publishable config, and Blade views—so it feels native to your stack while remaining easy to customize and extend.
- Seamless integration with the Lara Zeus package family
- Publishable configuration and views for full control
- Laravel-native service provider and Artisan support
- Lightweight, dependency-conscious design
- Blade-based UI that is simple to restyle
Frequently asked questions about Artemis
- What is lara-zeus/artemis and what does it add to Laravel?
- Artemis is the presentation layer for the Lara Zeus ecosystem: Blade views, Tailwind tokens and CSS, and a service provider that registers a Filament panel theme. It ships no models, migrations, routes, jobs, or third-party integrations, so its blast radius is limited to rendering. It exists to give Lara Zeus packages a consistent artistic look, not to add application features.
- How do I install lara-zeus/artemis in a Laravel project?
- Install it with Composer, publish its config, views, and assets, then register the theme on your Filament panel. Add the published view paths to your Tailwind content globs and rebuild your assets. The setup is measured in hours for an engineer who has registered a Filament theme before; the real cost is adapting the opinionated aesthetic to your brand and accessibility requirements.
- Which Laravel, Filament, and Tailwind versions does Artemis support?
- The evaluation does not list the exact PHP, Laravel, Filament, or Tailwind constraints, so check the package composer.json against your pinned majors before installing. What is clear is that there has been no Filament v4 work and no Tailwind v4 work. If you are mid-migration to either major, defer adoption rather than straddling breaking changes without upstream support.
- Is lara-zeus/artemis still maintained?
- No. The repository is archived, the last release is v1.0.10 from March 7, 2025, and it has 2 stars, 0 dependents, and a 0.155 health score. There is no CVE response, no Filament or Tailwind v4 work, and no upstream to absorb breaking changes. Treat it as a design reference or an MIT fork you own, not a live dependency.
- Can I use Artemis with plain Filament or a custom Blade admin panel?
- Effectively no. Fit is binary: high if your admin surface already runs the Lara Zeus family such as bolt, thunder, rhea, sky, athena, hermes, and cron, and close to zero on plain Filament or custom Blade. Confirm your Zeus inventory before spending engineering time, and skip it if you are not already in that ecosystem.
- How do I register the Artemis theme on a Filament panel?
- Publish the package config, views, and assets, then register the theme through the package service provider on your panel. Add the published view paths to your Tailwind content globs and rebuild assets so the theme classes are generated. Review the Blade views before first render, because they execute PHP inside an authenticated admin panel.
- How do I test that Artemis styles will work in production?
- Add the published view paths to your Tailwind content globs, rebuild, and audit the built CSS for a known theme class before trusting the build. Classes in unscanned vendor Blade files simply do not exist, and the failure mode is silent and visual: correct in npm run dev, half-styled in production. Compare a production build against your dev environment on the actual panel routes.
- What changed in lara-zeus/artemis v1.0.10 and will it break my icons?
- v1.0.10 removed iconpark, which degrades icons without throwing an error when upgrading from 1.0.9 or earlier. The breakage is visual, so inspect icon rendering after the upgrade. Also avoid vendor:publish --force, which will clobber your local edits to published views and assets.
- Will Artemis collide with Zeus package views I have already customized?
- Possibly, and this is the first thing to check. Build a collision inventory listing which Zeus packages and view namespaces Artemis overrides, then compare it with the views you have customized. If collisions are significant, fork the theme and resolve overrides in your own namespace rather than layering upstream overrides on top.
- Should I fork lara-zeus/artemis instead of requiring it with Composer?
- Yes, for production use. Copy the package into your monorepo under your vendor namespace, point Composer at it with a path repository and symlink true, and drop the upstream requirement. Record ownership and rationale in your service catalog so a future engineer does not reinstall the archived original, and pin versions explicitly rather than using a caret range.
Weaver
How can I help you explore Laravel packages today?