Wp Cli Valet Command Laravel Package

Product Decisions This Supports

• Developer environment standardization (local dev DX): wp-cli-valet-command extends WP-CLI with wp valet subcommands so a WordPress site can be linked, unlinked, and served through Laravel Valet with a single command instead of manual valet link, host file, and database juggling. This directly supports decisions about how engineers spin up WordPress sites locally.
• Build vs. buy for internal tooling: The alternative to adopting this is writing and maintaining in-house scripts (or Makefile targets) that wrap Valet. This package is a thin, purpose-built wrapper — evaluate it against the cost of owning equivalent shell glue.
• Onboarding time and time-to-first-commit: A one-command site link reduces per-engineer setup steps, which is a measurable DX metric (minutes from git clone to running site).
• Hybrid WordPress + Laravel estates: Teams already using Valet for Laravel get a consistent local dev story across both stacks, reducing the number of local environment tools supported by platform/DevEx teams.
• CI/local parity and scripted workflows: Because it is a WP-CLI command, site linking can be scripted and included in bootstrap scripts or documented runbooks rather than left to tribal knowledge.
• Roadmap relevance: Only relevant if WordPress plugin/theme/site development is on the roadmap and the team is standardized on macOS + Valet. Not a customer-facing capability; treat as a DevEx/platform dependency.

When to Consider This Package

Adopt when most of the following are true:

• Your team develops WordPress sites/plugins/themes and already uses Laravel Valet (macOS) as its local environment.
• WP-CLI is part of your standard toolchain, and you want site linking to be scriptable and repeatable rather than manual.
• You want a small, single-purpose dependency rather than adopting a heavier environment orchestrator.
• You value an actively maintained package: v1.3.1 adds GitHub Actions CI (a positive maintenance/quality signal) and fixes PHP deprecation notices, indicating ongoing compatibility work with modern PHP versions.
• You need the documented prerequisite made explicit: sites must be registered with Valet (the v1.3.1 docs clarification) — factor this into setup docs and onboarding.

Look elsewhere when:

• Your team is not on macOS/Valet (Windows, Linux, or cross-platform teams) — prefer Docker-based tooling such as DDEV, Lando, @wordpress/env, or wp-env.
• You need production or staging provisioning — this is a local development convenience only.
• You require enterprise support, SLAs, or a multi-maintainer governance model — this is a narrowly scoped community package (effectively single-maintainer); assess bus-factor risk.
• Your environment story already mandates an orchestrator with database, SSL, and version-pinning guarantees that Valet+this command doesn't provide.
• You need features beyond link/unlink (e.g., multisite orchestration, containerized service definitions) — you'd end up building around it anyway.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, low-risk developer-productivity tool, not a product feature. It removes manual steps from setting up WordPress sites on engineers' laptops, which shortens onboarding and reduces "works on my machine" friction. The v1.3.1 release is a maintenance patch — documentation clarification, added continuous integration, and PHP deprecation fixes — with no breaking changes and no migration work. It signals the package is still maintained. Cost of adoption is a single dev dependency; cost of not adopting is continued manual setup or bespoke scripts we'd have to own.

For engineering: Safe to adopt if you're on macOS + Valet + WP-CLI. wp valet gives you scriptable, repeatable site linking (wp valet link / unlink) instead of hand-edited Valet links and hosts entries. v1.3.1 fixes PHP deprecation notices, so it's cleaner on modern PHP — pin to ^1.3 and verify on your PHP version during rollout. Note the prerequisite that the site must be registered with Valet; add it to your bootstrap docs. Recommend a short spike: one engineer validates against a representative site, then we document it in the local-setup runbook.

Decision recommendation: Adopt as an optional, documented convenience for Valet-based WordPress developers; do not make it a hard requirement for teams on Docker-based environments, and keep a fallback of documented manual valet link steps to mitigate the single-maintainer risk.