Addon Field Type Laravel Package

Product Decisions This Supports

• CMS/admin content modeling: Supports decisions about whether to expose an “addon dropdown” field type inside an Anomaly/PyroCMS-style Streams Platform admin experience.
• Build vs. buy/extend: If already on the Anomaly/Streams ecosystem, this package may save a small amount of custom field-type work; otherwise it is too narrow to justify adoption.
• Roadmap prioritization: Low stars, zero dependents, and a single-purpose addon field indicate this should not drive roadmap investment or platform strategy.
• Extension ecosystem evaluation: Useful as a signal for whether the surrounding Anomaly addon ecosystem is active enough to rely on for product features.
• Use-case fit: Only relevant when product requirements include selecting an addon from a dropdown within a CMS field configuration; it is not a general Laravel form component.

When to Consider This Package

• Consider it only if the product is already built on Anomaly Labs / PyroCMS / Streams Platform and needs a field type that renders an addon dropdown.
• Consider it as a reference implementation or fork candidate if engineering wants to understand how addon field types are structured in that ecosystem.
• Look elsewhere if the product uses standard Laravel, Filament, Nova, Livewire forms, or a custom admin stack; native select/relationship fields will be simpler and better supported.
• Look elsewhere if the requirement is a maintained, broadly adopted package: 1 star, 0 dependents, and a narrow description indicate low community validation and likely limited maintenance.
• Avoid making it a critical dependency without a code audit, ownership plan, and fallback implementation.

How to Pitch It (Stakeholders)

Executive summary: This is a very small MIT-licensed addon field type for the Anomaly/PyroCMS ecosystem. It is not a strategic platform dependency and has effectively no visible adoption. It may be useful only if we are already committed to that CMS stack and need this exact admin field; otherwise we should not spend roadmap time on it.

Engineering summary: Treat it as a narrow field-type implementation, not a reusable Laravel component. Validate compatibility with our Anomaly/Streams version, review the code, and be prepared to fork or replace it. For any modern Laravel admin stack, a native select or relationship field is the lower-risk path.