- What does lee-to/laravel-package-command do?
- It provides a Laravel Artisan command that scaffolds a new package for you. Instead of manually creating the directory structure, service provider, config file, and composer metadata, you run the command and start building your package logic right away.
- How do I install lee-to/laravel-package-command?
- Install it with Composer, typically as a development dependency because it is a scaffolding tool rather than a runtime package. Run composer require --dev lee-to/laravel-package-command and Laravel's package discovery should register the Artisan command for you.
- What Artisan command does this package provide for scaffolding?
- The package registers an Artisan command, but the exact signature can vary by version, so run php artisan list after installation to confirm the command name and arguments. You generally pass the vendor and package name so the command can generate the matching folder structure and composer metadata.
- What files and folders does the generated package boilerplate include?
- According to the package description, it generates the boilerplate structure, a service provider, a config file, and composer files. That gives you the core pieces needed for a Laravel package without creating each file manually.
- Which Laravel versions are supported?
- The package's composer.json defines the supported Laravel and PHP version constraints, so check those before installing. Because it is a development-time scaffolding command, its compatibility mainly matters in your local and CI environments rather than in production runtime.
- Can I customize the generated package structure or stubs?
- You can always edit the generated files after scaffolding to match your preferred structure and coding style. If the package offers publishable stubs or configuration, review the README for those options before generating so you can tailor the output up front.
- Do I need lee-to/laravel-package-command in production?
- No, it is a development-time scaffolding tool, so you generally should not need it in production. Keep it in require-dev and exclude it from production deployments unless your workflow specifically requires running the command there.
- How do I test a package scaffolded with this command?
- After scaffolding, add tests the same way you would for any Laravel package, often using Orchestra Testbench or your preferred test setup. The generated composer.json gives you a place to configure autoload-dev and add PHPUnit, Pest, or other test dependencies.
- What are alternatives to using this package for Laravel package development?
- You can scaffold a package manually by creating the composer.json, service provider, config file, and directory structure yourself. Other package skeleton tools and starter repositories also exist, but this package's value is automating that boilerplate directly from an Artisan command.
- Is lee-to/laravel-package-command actively maintained and how do I update it?
- Check the repository's release history and composer.json for the latest version and maintainer activity. Update it with composer update lee-to/laravel-package-command, and review the changelog for changes to generated stubs or command behavior since it only affects scaffolding.