Product Decisions This Supports

This package is only relevant for legacy migration scenarios where projects are stuck on PHP <8.1 and cannot upgrade immediately. For all new projects, PHP 8.1+ native enums make this package obsolete—product decisions should prioritize eliminating third-party enum dependencies entirely. Roadmap focus should shift to migration tooling (e.g., enum:to-native command) rather than new feature development for this package. Build-vs-buy analysis confirms native PHP enums are superior for maintainability and future compatibility.

When to Consider This Package

Only for existing projects running PHP <8.1 that cannot upgrade due to critical infrastructure constraints (though upgrading PHP is strongly recommended). Never consider for new projects—PHP 8.1+ native enums are built-in, zero-dependency, and fully supported. If already using this package, focus exclusively on migration to native enums rather than adopting new features. Look elsewhere (native PHP enums) for all new development; this package adds unnecessary technical debt when modern alternatives exist.

Executives: PHP 8.1+ natively supports enums, making this package redundant. Continuing to use it introduces avoidable maintenance costs and technical debt. Migrating to native enums simplifies our stack, reduces dependency risks, and aligns with industry standards—freeing engineering resources for higher-value work. This is a low-effort, high-impact modernization step with immediate ROI.
Engineering: PHP's built-in enums provide identical functionality without third-party dependencies. Use the enum:to-native artisan command to automate migration of existing code. For new development, always prefer native enums—they're type-safe, zero-config, and fully compatible with Laravel 10+. This eliminates maintenance burden for an obsolete package while future-proofing our codebase.