- What is awcodes/filament-extras used for?
- It is presented as a collection of additional components and quality-of-life utilities for Laravel Filament admin panels. The description is generic, so treat it as a reference bundle for admin-panel UX ideas rather than a clearly scoped dependency. Review the source to enumerate the actual helpers and UI elements it provides.
- How do I install awcodes/filament-extras in Laravel?
- Run composer require awcodes/filament-extras in your Laravel project. The package uses Composer auto-discovery, so a service provider may register automatically. If it exposes a Filament plugin, add that plugin to your panel provider and publish any config or assets as documented. Because documentation is sparse, verify the exact steps in the README and source before installing in a real app.
- Does awcodes/filament-extras support Filament v3 or v4?
- The blurb mentions Filament v3, but the last release is dated 2023-04-07, before Filament v3 shipped, and there has been no release since. Do not assume v3 or v4 compatibility. Inspect composer.json for filament/filament constraints and test against your pinned Filament version in a throwaway branch.
- Is awcodes/filament-extras maintained?
- Treat it as unmaintained: the last release was April 2023, the repository has a single maintainer, 28 stars, and zero dependents. There is no evidence of recent triage or a current-major release. It is not clearly marked deprecated or archived, but the maintenance signal is weak.
- Is awcodes/filament-extras safe for production?
- Not as a direct production dependency. Zero dependents means no production field validation, and trait- or helper-based extras can fail silently through rendering or lifecycle drift. If you need a specific capability, spike it first, fork it under your own namespace, pin Filament, and add tests.
- How do I register the filament-extras plugin in a Filament panel provider?
- Check the package source for the plugin class name, then add it to the plugins array in your Filament panel provider. If the package relies only on auto-discovery, a service provider may handle registration without a panel plugin entry. Publish config or assets only if the package documents them, and verify with a local panel render.
- What Composer constraints does filament-extras require?
- The available context does not list exact PHP, Laravel, or Filament constraints. Inspect the package composer.json for require entries and run composer why-not awcodes/filament-extras to surface conflicts. Do not rely on the README blurb alone, especially given the April 2023 release date.
- Can filament-extras conflict with other Filament plugins or assets?
- Yes, it can collide on service-provider registration, view namespaces, or FilamentAsset::register calls. Skeleton packages also commonly break when autoload namespaces are changed after forking. Test in an isolated branch with your existing plugins, and use composer why-not to expose dependency conflicts.
- Should I fork awcodes/filament-extras or extract components?
- Forking or selective extraction is usually cleaner than adopting upstream directly. Fork under your organization namespace, pin the Filament version, rename the autoload namespace in composer.json and src, and add tests. Alternatively, copy only the helpers or UI patterns you need and discard the rest.
- What are alternatives to awcodes/filament-extras?
- Start with Filament core and actively maintained awcodes plugins such as Curator and Badge, which have clearer scopes and maintenance signals. Other community Filament plugins or in-house helpers may cover the same admin-panel UX needs. Because filament-extras has no meaningful description, compare actual source behavior before choosing an alternative.