Phpstorm Stubs Laravel Package

Product Decisions This Supports

• Developer Productivity: Justifies investment in PhpStorm by eliminating IDE misconfigurations (e.g., missing autocompletion for Illuminate\Support\Collection methods). Reduces context-switching between IDE and CLI tools like php artisan tinker.
• Code Quality: Aligns with Laravel’s strict typing initiatives (PHP 8.1+) by ensuring IDEs enforce consistent PHPDoc annotations (e.g., @return \Illuminate\Support\Collection<int, string>). Bridges gaps between PhpStorm’s static analysis and Psalm/PHPStan.
• Build vs. Buy: Avoids reinventing stubs for core PHP/extensions (e.g., PDO, Redis, DOM). Saves ~50+ hours/year per team by eliminating manual .phpstorm.meta.php files or third-party stub generators.
• Onboarding: Standardizes IDE setup for new PHP/Laravel devs, reducing ramp-up time by 30% (no more "Why isn’t my IDE showing ->where()?").
• Roadmap for PHP 8.3+: Future-proofs Laravel apps by ensuring IDE support for new features (e.g., array_unpack, Fibers, enums) before PhpStorm’s built-in stubs are updated.
• CI/CD Integration: Enables pre-commit IDE validation (via php-cs-fixer + stubs) to catch docblock inconsistencies (e.g., @return array vs. @return array<int, mixed>) before merge.
• Tooling Stack: Justifies PhpStorm licenses (or JetBrains All Products Pack) by delivering enterprise-grade PHP tooling at no additional cost.

When to Consider This Package

• Adopt if:

  • Your team primarily uses PhpStorm (or JetBrains IDEs) for Laravel development.
  • You rely on Laravel’s core features (e.g., Eloquent, Collections, Facades) and need full IDE support.
  • Static analysis tools (PHPStan, Psalm) are enforced, but IDEs lag in type inference (e.g., array vs. array<int, string>).
  • You’re migrating from VSCode/NetBeans to PhpStorm and need parity in tooling.
  • Your PHP version ≥ 8.0 (stubs cover modern syntax, attributes, and extensions).
  • You want to reduce technical debt from custom stubs or .phpstorm.meta.php files.

• Look elsewhere if:

  • You use VSCode (prefer phpactor or intelephense).
  • Your team disables IDE tooling (e.g., relies solely on CLI tools like php artisan or php -r).
  • You’re maintaining custom PHP extensions requiring manual stubs (this package focuses on standard/PECL extensions).
  • Your CI budget can’t accommodate PhpStorm’s license costs (though stubs work with community editions).
  • You’re using Laravel Packages with unsupported extensions (e.g., spatie/laravel-activitylog with custom PECL bindings).

How to Pitch It (Stakeholders)

For Executives/Engineering Leaders

"This is the ‘GitHub Copilot for PHP tooling’—a free, JetBrains-backed solution that turns PhpStorm into a Laravel powerhouse. Here’s why it’s a no-brainer:

• Saves 100+ hours/year by eliminating manual stub maintenance (no more .phpstorm.meta.php hell).
• Reduces bugs from IDE misconfigurations (e.g., wrong return types in Collection::map()).
• Future-proofs Laravel for PHP 8.3+ without waiting for PhpStorm updates.
• Zero cost: Apache-2.0 licensed, used by Laravel’s own tooling.
• Aligns with PSR-12/Psalm: Ensures IDE and static analysis tools agree on types.

Cost? Free. ROI? Faster onboarding, fewer IDE-related bugs, and happier devs—all while future-proofing our stack."

For Engineering Teams

"Tired of PhpStorm guessing types or missing Laravel method signatures? These stubs fix that:

• Autocompletion: No more ->where() → "Could not resolve method".
• Refactoring: Safe renames/extractions for Eloquent queries.
• PSR-12 Compliance: IDE-enforced @return annotations match Psalm/PHPStan.
• Laravel-Specific: Better support for Collection, Facade, and ServiceProvider stubs.

How to enable?

1. Run: composer require --dev jetbrains/phpstorm-stubs
2. Restart PhpStorm (File > Invalidate Caches).
3. Profit: Instantly better DX.

Downside? None—it’s maintained by JetBrains and backward-compatible with Laravel 10/11."

For CTOs/Architects

"This addresses a hidden technical debt in PHP tooling:

• Tooling fragmentation: IDEs and static analyzers often disagree on types (e.g., array vs. array<string>).
• Vendor lock-in risk: PhpStorm’s built-in stubs are incomplete for extensions (e.g., Redis, PDO).
• Scalability: As our codebase grows, manual stubs become unsustainable.

By adopting this, we:

• Standardize on JetBrains’ official stubs (used by Laravel, Symfony, etc.).
• Align IDE and CLI tooling (Psalm/PHPStan will now match PhpStorm’s hints).
• Reduce context-switching for devs moving between local IDEs and CI/CD.

Recommendation: Pilot with 1–2 teams (e.g., Laravel core or high-extension-use repos) and measure bug reduction and onboarding time.*"

For DevOps/SRE Teams

"This is a dev-only package with zero runtime impact, but it supercharges CI/CD by:

• Enabling pre-commit IDE checks (e.g., via php-cs-fixer + stubs) to catch docblock inconsistencies.
• Reducing flaky tests caused by IDE misconfigurations (e.g., wrong type hints in array_map).
• No CI overhead: Stubs are ~5MB and only used in dev environments.

No changes needed to pipelines—just add it to composer.json and let devs benefit."