Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Extension Command Laravel Package

wp-cli/extension-command

WP-CLI extension-command adds wp plugin and wp theme management: install, activate/deactivate, update, delete, and more. Supports bulk actions, multisite network activation, exclusions, and forcing reactivation to rerun hooks.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Automated Plugin/Theme Management: Enables programmatic lifecycle management (install, activate, update, deactivate, delete) for WordPress plugins/themes, reducing manual intervention in CI/CD pipelines or DevOps workflows.
  • Scalable WordPress Deployments: Supports multi-environment deployments (e.g., staging → production) with granular control over plugin states (e.g., --network for multisite).
  • Build vs. Buy: Avoids reinventing CLI tooling for WordPress by leveraging a battle-tested, community-maintained package with 90+ stars and MIT license.
  • Use Cases:
    • CI/CD Integration: Automate plugin updates or rollbacks in pipelines (e.g., GitHub Actions).
    • Managed Hosting: Streamline plugin management for shared hosting providers or SaaS platforms.
    • Local Development: Sync plugin states across local/dev/staging environments.
    • Security Patching: Bulk update plugins to mitigate vulnerabilities (e.g., --force for critical fixes).
    • A/B Testing: Dynamically activate/deactivate plugins for feature experiments.

When to Consider This Package

  • Adopt When:

    • Managing 50+ WordPress sites/plugins where manual updates are unscalable.
    • Requiring auditability (e.g., logs of plugin changes for compliance).
    • Needing fine-grained control (e.g., network-wide vs. site-specific activations).
    • Integrating with infrastructure-as-code (e.g., Terraform, Ansible) for WordPress.
    • Supporting multi-environment parity (e.g., dev/staging/prod plugin states).
  • Look Elsewhere If:

    • Your stack doesn’t use WordPress (this is WordPress-specific).
    • You need GUI-based management (consider WP Admin or plugins like WP-CLI UI).
    • Requiring advanced plugin customization (e.g., modifying plugin code post-install; use a custom script).
    • Legacy systems lack PHP/CLI support (e.g., Windows-only environments without WP-CLI installed).
    • Need real-time monitoring of plugin health (combine with tools like Health Check & Troubleshooting).

How to Pitch It (Stakeholders)

For Executives:

"This package lets us automate WordPress plugin management at scale—reducing manual errors, speeding up deployments, and cutting support costs. For example, we can now update 100+ plugins across all sites with a single CLI command, instead of logging into each dashboard. It’s like Git for WordPress plugins: version control, rollbacks, and consistency across environments. The MIT license and WP-CLI’s adoption (used by 1M+ WordPress sites) ensure reliability, while the --force and --network flags give us control over critical updates and multisite setups."

ROI:

  • Time Saved: 80% reduction in plugin management tasks.
  • Risk Reduction: Audit trails for plugin changes (e.g., compliance, security).
  • Scalability: Supports 10x more sites without manual overhead.

For Engineering/DevOps:

*"This is a Swiss Army knife for WordPress plugins—built into WP-CLI, so it’s already in our stack. Key perks:

  • Idempotent Operations: Safe to rerun (e.g., wp plugin install --force for updates).
  • Dependency Management: Auto-install required plugins (--with-dependencies).
  • CI/CD Friendly: Exit codes for scripting (e.g., fail pipelines if a plugin isn’t active).
  • Multisite Support: Manage plugins across networks with --network.

Example Workflow:

# Update all plugins in staging, then promote to prod
wp plugin update --all --skip-update-check  # Dry run
wp plugin update --all --version=stable     # Prod

Why Not Build?

  • Already maintained by the WP-CLI team (90+ stars, MIT license).
  • Handles edge cases (e.g., PHP requirements, TLS retries).
  • Integrates with our existing wp CLI tooling."

Tech Deep Dive:

  • Language: PHP (native to WordPress).
  • Testing: 100% test coverage (PHPUnit/Behat).
  • Extensible: Hook into WordPress’s plugin API for custom logic.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
andydefer/laravel-cluster
testo/fiber
mintobit/jobqueue
a4sex/maintenance-bundle
a4sex/entity-date-update
a4sex/client-identifier
a4sex/base-utilites
a4sex/key-value-storage
a4sex/micro-status
chilldev/dependency-injection-extra
datinglibre/datinglibre-app-api
biberltd/corebundle
bricre/symfony-bundle-test
biberltd/logbundle
dominium/http-adapter-bundle
dominium/google-analytics
a4sex/auto-clean-entity
christhompsontldr/laravel-inky
spatie/mailcoach-vapor
spatie/laravel-javascript-views