Git Php Laravel Package

Getting Started

1. Verify PHP Compatibility: Ensure your project uses PHP 8.0+ (PHP 5.6-7.3 is no longer supported). Run:

   php -v
   

   Update your project if needed (e.g., via phpbrew, Docker, or server config).
2. Install/Update the Package:

   composer require vendor/package:^4.4.0
   

3. First Use Case: Test basic functionality (e.g., a core feature like model binding, API responses, or middleware) to confirm compatibility. Example:

   use Vendor\Package\Facades\Feature;
   
   Feature::doSomething(); // Replace with your package's entry point
   

Implementation Patterns

PHP 8.4 Optimizations

• Leverage PHP 8.4’s new features (e.g., array_unpack improvements, str_contains optimizations) if the package exposes public APIs for custom logic.
• Type Safety: The package now aligns with stricter PHPStan rules. Review type hints in your custom integrations (e.g., service providers, event listeners) to avoid runtime errors.

Workflow Integration

1. Service Providers: If extending the package, ensure your register()/boot() methods use PHP 8.4+ syntax (e.g., static first-class callable syntax for closures).

   public function boot(): void {
       // PHP 8.4+ compatible
   }
   

2. Dependency Injection: Prefer constructor injection with typed properties for new components:

   public function __construct(private SomeService $service) {}
   

3. Testing: Update test suites to use PHPUnit 10+ (recommended for PHP 8.4) and enable PHPStan level 9+ for stricter checks.

Gotchas and Tips

Breaking Changes

• PHP 5.6-7.3 Drop: Projects using these versions will fail. Check composer.json for global constraints or use:

  composer why-not vendor/package:^4.4.0
  

• PHPStan Errors: If you extended the package, resolve warnings by:
  • Adding @mixin or @method annotations for dynamic methods.
  • Updating return types in custom classes (e.g., array<int, Model> → array<int, class-string>).

Debugging Tips

• Deprecated Features: Run composer why vendor/package to identify indirect dependencies blocking upgrades.
• PHP 8.4-Specific Issues:
  • Enable strict_types=1 in composer.json to catch implicit type coercion.
  • Use php -dzend.assertions=1 to catch assertion errors during development.

Extension Points

• Custom Middleware: If writing middleware, use PHP 8.4’s Closure::fromCallable() for cleaner syntax:

  $middleware->append(fn () => new YourMiddleware());
  

• Event Listeners: Prefer array_unpack for variadic arguments in listeners:

  public function handle(object $event, ...$args) {
      [$arg1, $arg2] = array_unpack($args);
  }
  

• Performance: PHP 8.4’s JIT compiler may improve package performance. Test with opcache.jit_buffer_size=100M in php.ini.

Configuration Quirks

• Environment Variables: If the package uses .env values, ensure they’re cast to PHP 8.4-compatible types (e.g., bool instead of string for flags).
• Legacy Code: Use php -l to lint custom files for syntax errors before upgrading.