Laravel Helpers Laravel Package

Product Decisions This Supports

• Build vs. buy for shared Laravel plumbing. Helper discovery/autoloading is commodity infrastructure. This release makes the buy case stronger: helper:validate (syntax checks + duplicate function detection) and logged failed loads replace custom bootstrap code and the tribal knowledge that goes with it.
• Platform baseline decisions. v3 requires PHP ^8.3. That is a roadmap-level constraint, not an incidental dependency bump — it forces a scheduled upgrade decision for any app still on 8.1/8.2, and it should be sequenced deliberately rather than discovered mid-sprint.
• Reliability investment with a measurable signal. Failed helper file loads are now tracked and logged (log_errors config), converting a class of silent production failures — a helper that quietly doesn't register in one deployment target — into an observable event. This is a concrete reduction in mean-time-to-diagnose.
• CI / release-gate hardening. helper:validate and duplicate-function detection target a deployment-killer failure mode (fatal Cannot redeclare function). Adding it as a pipeline step is a cheap, high-leverage quality gate.
• Developer onboarding and velocity. make:helper with a declare(strict_types=1) stub, plus helper:reload for local iteration, standardizes "where do global functions live and how are they written" across squads — a defensible DevEx spend, not just ergonomics.
• Tooling and internal dashboards. helper:list --json with function counts and failed status makes helper inventory reportable to an internal developer portal or health dashboard.
• Vendor/quality governance. PHPStan level 5 and Pint in upstream CI lowers the maintenance-risk estimate we attach to accepting the dependency.
• Operational documentation work. The publish tag changed to helpers-config. That is a small but real work item: deploy runbooks, provisioning scripts, and starter-kit setup docs must be updated or new environments will silently publish nothing.

When to Consider This Package

Adopt when:

• You run multiple Laravel apps or an internal starter kit and want one consistent, validated convention for global helper files.
• You already rely on global helper functions and have hit duplicate-function fatals or "helper didn't load in this environment" incidents.
• Your platform is already on PHP 8.3+, or that upgrade is already committed on the roadmap — this is the hard gate.
• You want the validation and listing output wired into CI or an internal dashboard (helper:list --json).
• You are comfortable with spatie/laravel-package-tools as a transitive dependency — it is a mainstream, widely deployed package, so the marginal supply-chain risk is low for most teams.

Look elsewhere, or defer, when:

• You cannot move to PHP 8.3 in the near term. Staying on v2.1.0 means maintaining an unpatched line; price that before deciding to defer, don't let it happen by default.
• The actual need is three or four functions. A plain files entry in composer.json autoload is sufficient and carries zero dependency cost.
• You have a strict minimal-dependency policy or a per-release vendor audit process that would make every upgrade a procurement exercise.
• Your architecture intentionally avoids global functions in favor of classes and facades — this package institutionalizes exactly what you are trying to eliminate.
• It is a single small application with no reuse horizon; the config tag, extra command surface, and new dependency outweigh the benefit.

How to Pitch It (Stakeholders)

For executives: This is a low-risk, MIT-licensed maintenance upgrade for our Laravel foundation. It converts a class of silent production failures into logged, diagnosable events, and adds automated checks that catch the two most common causes of deployment-time fatal errors before they ship. There is no licensing cost. The one real prerequisite is moving our PHP baseline to 8.3, which should already be on the platform roadmap; the dependency additions are mainstream and low risk. Recommend adoption, sequenced behind the PHP upgrade.

For engineering: v3 is a quality release rather than a feature release. Failed helper loads are logged, and helper:validate catches syntax errors and duplicate function definitions — the fatal-error class that has burned us. helper:list --json enables reporting, helper:reload shortens the local feedback loop, generated stubs now include declare(strict_types=1), and CI runs PHPStan level 5 plus Pint so quality is enforced upstream rather than in review. Breaking changes are narrow and mechanical: bump to PHP ^8.3, add spatie/laravel-package-tools, and change the publish invocation to --tag=helpers-config. Suggested rollout: pilot in the starter kit, update runbooks and provisioning scripts, verify helper load order and log_errors defaults match current behavior, add helper:validate to CI, then roll out. Budget roughly half a day of platform work for the baseline bump and documentation.