Weave Code
Installer Laravel Package
package-wizard/installer
Package Wizard Installer provides an interactive CLI wizard for Laravel packages, simplifying installation by handling common setup steps like publishing config and assets, running migrations, and registering service providers.
Package Wizard is a composer plugin for creating a new packages using CLI tool.
Frequently asked questions about Installer
- What does package-wizard/installer actually do?
- It adds an Artisan-driven interactive setup wizard to Laravel packages. The wizard guides users through common install steps such as publishing config and assets, running migrations, and registering service providers. Package authors declare composable steps, and the installer sequences them with prompts and sensible defaults. It is developer tooling, not runtime application infrastructure.
- How do I install package-wizard/installer for a Laravel package?
- Add it as a Composer dependency in the package repository, typically under require-dev rather than in an application's production requires. Then register the install command through your package service provider and define the steps the wizard should run. Because the package is archived, pin a version and validate it against your current Laravel and PHP versions first. Do not assume upstream compatibility fixes.
- Is package-wizard/installer compatible with Laravel 10 or Laravel 11?
- Its last release was in May 2021, so it predates Laravel 9, 10, and 11 baselines and modern PHP 8.1+ requirements. The composer.json version ceilings are likely to conflict with current projects, and its Symfony Console interaction layer may need work. Treat compatibility as unproven and run a spike with composer why-not before adopting it. For greenfield work, reimplementing the flow with laravel/prompts is safer.
- Does package-wizard/installer work in CI or non-interactive environments?
- Interactive wizards are a common CI failure point because prompts can block or fail in non-TTY contexts such as container builds and scripted provisioning. There is no evidence in the package context of a robust --no-interaction path with safe defaults. You must test this explicitly before relying on it in automation. If it cannot degrade gracefully, keep it out of CI and use a flag-driven install command instead.
- Is package-wizard/installer still maintained?
- No. The repository is archived, the last release was 2021-05-25, and it has low adoption signals, so it is effectively unmaintained. Any integration means owning the code and assuming zero upstream fixes. The MIT license makes a private fork feasible if the pattern is valuable to you. Otherwise, a first-party install command is the lower-risk option.
- Can I customize the prompts and installation steps in package-wizard/installer?
- Yes, the package is designed around customizable stubs for each installation step and composable steps that can be reused across packages. Package authors declare the steps, and the installer runs them in a guided sequence with sensible defaults. That small surface area is why a fork or reimplementation is measured in days rather than weeks. Validate any customization against your supported Laravel and PHP matrix.
- Are package-wizard/installer install steps idempotent?
- Idempotency is a medium risk, not a guaranteed property. Publishing config and running migrations or seeders in a guided flow can overwrite customized config on a re-run or execute destructive steps without a dry-run. There is no evidence of transactional rollback in the package context. Review and guard each step, especially publish and migrate, before using it on existing projects.
- How can I test a package-wizard/installer wizard automatically?
- The flow should be exercisable through Laravel's Artisan command assertion helpers if the install command is registered and can run non-interactively. However, interactive prompt flows are often only testable by hand unless you add a flag-driven or mocked input path. There is no evidence the package provides a test-friendly contract out of the box. Plan a spike that runs the command under artisan test with --no-interaction or equivalent.
- What are good alternatives to package-wizard/installer?
- The strongest alternative is a native php artisan vendor:install command built on laravel/prompts, with a documented step contract for publish, migrate, and confirmation. That delivers most of the value with no abandonment risk and fits current Laravel versions. If you specifically want the existing pattern, fork the MIT-licensed package and reimplement the interaction layer on laravel/prompts. Keep the scope to developer tooling and require-dev.
- Should package-wizard/installer be a production dependency?
- No. It is a developer-experience layer for package installation, so it should be scoped to require-dev in package repositories and never installed into production application images. It does not belong in an application's composer.json requires as runtime infrastructure. If you adopt the pattern, keep the install command out of request-path code and gate it to local or build-time use.
Weaver
How can I help you explore Laravel packages today?