Console Components Laravel Package

Product Decisions This Supports

• Developer tooling & DX roadmap: Supports investment in first-party CLI experience — install/upgrade wizards, artisan scaffolding generators, data-import/migration helpers, and ops runbooks delivered as guided prompts instead of wiki pages.
• Build vs. buy: Strong lean toward adopt over build for console UI primitives. The package is a thin, opinionated layer over Laravel Prompts; re-implementing consistent prompt/table/alert components in-house is low-differentiation work with ongoing maintenance cost.
• Feature sequencing: Enables CLI-driven onboarding and self-service admin flows to ship earlier, without waiting on a web UI. Useful for internal tools and B2B/ops-facing workflows where a terminal is already the working surface.
• Risk posture for 1.0.4: Patch-level release, no breaking changes, no deprecations, no migration work. It tracks upstream Laravel Prompts API changes — a positive maintenance signal that reduces version-drift risk when the Laravel ecosystem bumps Prompts. No roadmap re-planning required; treat as routine upgrade.
• Where it does not inform decisions: This release says nothing about the package's long-term support model, test coverage, or maintainer depth. Those remain open diligence items, not resolved by a compat patch.

When to Consider This Package

Adopt when:

• You are on Laravel and already standardizing on Artisan + Laravel Prompts, and want consistent look-and-feel across many commands rather than ad-hoc prompt code.
• You have multiple commands/teams producing CLI UX and need shared, reusable components to avoid drift.
• Your CLI needs are mainstream: prompts, confirmations, selects, tables, alerts, progress — not full-screen TUIs.
• You want to move fast on internal tooling and accept a small-surface dependency.

Look elsewhere when:

• You need rich terminal UIs, layout control, or event-driven rendering — go direct to Symfony Console / Termwind.
• You are not on Laravel, or you have pinned an older Prompts major and cannot move.
• Procurement requires vendor SLAs, security review artifacts, or guaranteed LTS — this is a single-maintainer open-source package; assess bus factor and pin ^1.0 accordingly.
• The abstraction is thinner than your needs: if you only need one or two prompts, using Laravel Prompts directly avoids a dependency entirely.
• You require a stable public API contract across majors; the 1.0.x line is young and upstream-coupled.

Diligence before adoption: confirm the Laravel/Prompts version matrix (1.0.4 exists specifically to align Prompts support), and verify your supported Laravel range is covered.

How to Pitch It (Stakeholders)

To executives: A free, MIT-style Laravel package that lets us ship polished command-line setup and admin tools faster. The 1.0.4 release is a small compatibility fix that keeps it aligned with Laravel's own prompt library — no breaking changes, no migration cost, no licensing spend. Upside is faster internal tooling and self-service ops flows; downside is a small single-maintainer dependency, which we mitigate by pinning versions and keeping usage to non-critical tooling paths.

To engineering: Idiomatic Laravel, builds on Prompts rather than replacing it, so it stays close to the framework's grain. 1.0.4's only change is a Prompts support update plus a first-time contributor — evidence the package is being kept current with upstream. Low integration cost: one dependency, no service provider gymnastics expected beyond standard package discovery. Recommended posture: pilot on one or two internal commands, pin ^1.0, and revisit if we hit component gaps that push us toward raw Symfony Console.