如何通过Composer在其他项目中复用自定义Laravel命令？

Absolutely! You can absolutely reuse your custom Laravel command across multiple projects with Composer—this is actually one of the best ways to share reusable Laravel components. Here's a step-by-step breakdown of how to do it:

Option 1: Package your command as a proper Composer package (Recommended) #

This is the cleanest, most scalable approach if you plan to use the command across multiple projects long-term.

1. Set up the package structure
   Create a new directory for your package (outside your existing Laravel project), e.g., my-custom-command-package. Inside it, run:

   composer init
   

   Fill in the prompts—make sure to set the type to laravel-package (or library if you prefer) and define your vendor name (like your GitHub username) and package name.

2. Move your command and add a service provider

   • Copy your custom command file into src/Commands/ (create the directories if needed). Update the namespace at the top of the command to match your package, e.g., namespace YourVendor\MyCustomCommand\Commands;.
   • Create a service provider in src/CommandServiceProvider.php to register your command with Laravel:

     <?php
     
     namespace YourVendor\MyCustomCommand;
     
     use Illuminate\Support\ServiceProvider;
     use YourVendor\MyCustomCommand\Commands\YourCustomCommand;
     
     class CommandServiceProvider extends ServiceProvider
     {
         public function boot()
         {
             if ($this->app->runningInConsole()) {
                 $this->commands([
                     YourCustomCommand::class,
                 ]);
             }
         }
     }
     

3. Update composer.json
   Add autoload rules and Laravel provider metadata to your package's composer.json:

   {
       "name": "your-vendor/my-custom-command",
       "type": "laravel-package",
       "autoload": {
           "psr-4": {
               "YourVendor\\MyCustomCommand\\": "src/"
           }
       },
       "extra": {
           "laravel": {
               "providers": [
                   "YourVendor\\MyCustomCommand\\CommandServiceProvider"
               ]
           }
       },
       "require": {
           "laravel/framework": "^8.0|^9.0|^10.0" // Match your supported Laravel versions
       }
   }
   

4. Publish and install

   • Push your package to a Git repository (GitHub, GitLab, etc.), then submit it to Packagist if you want it publicly available.
   • In any target Laravel project, install it with:

     composer require your-vendor/my-custom-command
     

   Laravel will automatically register the service provider, and your command will be available via Artisan.

Option 2: Local reuse (for development/testing) #

If you just want to test the command across local projects without publishing it, use a local path repository:

1. In your target project's composer.json, add a local repository entry pointing to your package directory:

   "repositories": [
       {
           "type": "path",
           "url": "../path/to/your-command-package"
       }
   ]
   

2. Install the package with:

   composer require your-vendor/my-custom-command:@dev
   

   Composer will create a symlink to your local package, so any changes you make to the command will reflect immediately in the target project.

Option 3: Use a Git repository directly #

If you don't want to publish to Packagist, you can pull the package directly from a Git repo:

1. Add the Git repository to your target project's composer.json:

   "repositories": [
       {
           "type": "vcs",
           "url": "https://github.com/your-username/my-custom-command.git"
       }
   ]
   

2. Install it with:

   composer require your-vendor/my-custom-command:dev-main
   

   (Replace dev-main with your actual branch name.)

Quick Notes #

• Double-check that your command's namespace matches what you defined in the package's autoload rules.
• Make sure to specify compatible Laravel versions in your package's composer.json to avoid conflicts.
• If your command relies on other dependencies, add them to the package's require section.

内容的提问来源于stack exchange，提问作者user9490882