- What is Package Wizard used for?
- Package Wizard is a development-time CLI for scaffolding new Laravel and PHP packages. It asks setup questions and generates boilerplate such as composer.json, a service provider, config stubs, tests, and docs. It is not a runtime library and should not be added to application production dependencies.
- How do I install Package Wizard?
- Install it through Composer using the package name andrey-helldar/package-wizard, typically as a development or global CLI tool. Because the package is archived and last released in May 2021, pin a specific version rather than relying on an unpinned global install. Verify the generated output against your team's PHP and Laravel standards before using it broadly.
- Does Package Wizard support Laravel 10 and 11?
- Compatibility with Laravel 10 and 11 is not guaranteed. The last release was May 2021, so the generated templates may predate current Laravel package conventions. Run a spike and validate Composer constraints, service-provider registration, config publishing, and test bootstrap against your supported matrix.
- Is Package Wizard still maintained?
- No. The repository is archived and the last release was in May 2021. Do not treat it as a maintained upstream dependency without an internal fork or replacement plan.
- Can Package Wizard be used in CI or automated workflows?
- Package Wizard is designed around interactive prompts, which makes fully automated CI use awkward. Evaluate whether prompts can be scripted or bypassed for your workflow. For repeatable CI or template regeneration, an internally owned skeleton or a fork is usually the better path.
- Does Package Wizard add runtime dependencies to my Laravel app?
- No. Package Wizard is used only during scaffolding and does not affect application runtime architecture or deployment topology. The generated package code may still need review, but the tool itself should not be a production dependency.
- Can I customize the boilerplate Package Wizard generates?
- You can fork the tool or extract the generated skeleton into an internally owned, versioned package template. Then patch the templates for your supported PHP, Laravel, PHPUnit or Pest, and Composer versions. Assign ownership for updates when Laravel and PHP conventions change.
- What are good alternatives to Package Wizard?
- The evaluation recommends using Package Wizard as a reference implementation or short-term accelerator, then moving to an internally owned package template. That can be a forked version of the tool or a golden skeleton in a template repository. Teams with mature standards may prefer a Composer create-project template or manual scaffolding.
- Can Package Wizard scaffold non-Laravel PHP packages?
- It is less clean for non-Laravel PHP packages. The tool aligns best with Laravel and Composer conventions such as PSR-4 autoloading, service providers, config stubs, and PHPUnit-style tests. Non-Laravel packages can still borrow the generated structure, but service-provider and config boilerplate may be unnecessary.
- What license does Package Wizard use, and can I fork it?
- The technical evaluation references an MIT license, but confirm the license in the repository before forking or redistributing. If compatible with your policy, an internal fork is the recommended way to own template quality and updates. Document the fork, pin versions, and track changes needed for current Laravel and PHP conventions.