Composer Bridge Laravel Package

Getting Started

Minimal Setup

1. Installation:

   composer require mopa/composer-bridge
   

   Add to your composer.json under extra:

   "bridge": {
       "symfony": {
           "dir": "vendor/symfony"
       }
   }
   

2. First Use Case: Use the bridge to load Symfony components without requiring the full Symfony framework. Ideal for Laravel projects needing Symfony’s HttpFoundation, Console, or DependencyInjection without bloat.

   Example in config/app.php:

   $loader = require __DIR__.'/../../vendor/autoload.php';
   $bridge = new \Mopa\ComposerBridge\Bridge\Bridge($loader);
   $bridge->register();
   

   Now access Symfony classes directly:

   use Symfony\Component\HttpFoundation\Request;
   $request = Request::createFromGlobals();
   

Implementation Patterns

Workflow Integration

1. Dependency Isolation:

   • Use the bridge to load Symfony components in a compartmentalized way (e.g., for API routes or CLI commands).
   • Example: Load Symfony\Component\Console only in app/Console/Kernel.php:

     $bridge = new \Mopa\ComposerBridge\Bridge\Bridge(require __DIR__.'/../../../vendor/autoload.php');
     $bridge->register();
     use Symfony\Component\Console\Application;
     

2. Autoloading Optimization:

   • Combine with Laravel’s composer.json autoloading to avoid conflicts:

     "autoload": {
         "psr-4": {
             "App\\": "app/",
             "Symfony\\": "vendor/symfony"  // Explicitly map Symfony namespaces
         }
     }
     

3. Service Container Integration:

   • Bind Symfony services to Laravel’s container via register() in a service provider:

     public function register()
     {
         $bridge = new \Mopa\ComposerBridge\Bridge\Bridge($this->app->get('loader'));
         $bridge->register();
         $this->app->singleton('symfony.event_dispatcher', function () {
             return new \Symfony\Component\EventDispatcher\EventDispatcher();
         });
     }
     

Common Use Cases

• HTTP Handling: Use HttpFoundation for request/response objects in middleware or controllers.
• Console Tools: Leverage Symfony\Component\Console for CLI tools without installing Symfony CLI.
• Dependency Injection: Use Symfony\Component\DependencyInjection for complex service wiring.

Gotchas and Tips

Pitfalls

1. Namespace Collisions:

   • Symfony’s Symfony\Component\* namespaces may conflict with Laravel’s or other packages. Solution: Use fully qualified namespaces (e.g., \Symfony\Component\HttpFoundation\Request) or alias them in composer.json:

     "autoload": {
         "psr-4": {
             "Symfony\\": "vendor/mopa-bridge/symfony"
         }
     }
     

2. Bridge Registration Timing:

   • Register the bridge after Laravel’s autoloader but before first use. Avoid lazy-loading issues by calling $bridge->register() early in the bootstrap process (e.g., in bootstrap/app.php).

3. Symfony Version Mismatches:

   • The bridge may not support the latest Symfony versions. Tip: Check the release notes and pin versions in composer.json:

     "require": {
         "symfony/http-foundation": "^5.4"
     }
     

Debugging

• Class Not Found Errors:

  • Verify the bridge is registered and Symfony’s autoload paths are correct. Run:

    composer dump-autoload
    

  • Check for typos in namespace usage (e.g., Symfony\Component\HttpFoundation\Request vs. Symfony\Component\HttpFoundation\Requests).

• Performance Overhead:

  • The bridge adds minimal overhead, but excessive use of Symfony components may bloat your app. Tip: Load only what you need (e.g., avoid pulling in symfony/framework-bundle).

Extension Points

1. Custom Bridge Config:

   • Extend the bridge for custom Symfony paths or aliases. Example:

     $bridge = new \Mopa\ComposerBridge\Bridge\Bridge($loader, [
         'symfony' => [
             'dir' => 'custom/vendor/symfony',
             'aliases' => [
                 'Symfony\Component\HttpFoundation' => 'Symfony\HttpFoundation'
             ]
         ]
     ]);
     

2. Integration with Laravel Mix:

   • Use Symfony’s Filesystem component in build scripts:

     use Symfony\Component\Filesystem\Filesystem;
     $fs = new Filesystem();
     $fs->dumpFile('public/mix-manifest.json', file_get_contents('public/mix-manifest.json'));
     

3. Testing:

   • Mock Symfony dependencies in tests by resetting the bridge or using Laravel’s MockApplication. Example:

     $bridge->reset(); // If supported by your version