Weave Code
Wp Steroids Laravel Package
metabolism/wp-steroids
WP Steroids is a Laravel-inspired framework for WordPress plugins, adding service providers, dependency injection, routing, and Eloquent-style models. Build maintainable, testable plugins with familiar PHP patterns, Composer-ready structure, and less boilerplate. Designed for modern WordPress develo...
WP Steroids is a modern foundation for WordPress plugin and theme development, bringing Laravel-inspired structure to traditional WordPress code. It helps organize bootstrapping, services, and configuration so projects stay maintainable as they grow.
- Service container and dependency injection for cleaner code
- Service providers for modular bootstrapping
- Configuration management for plugin and theme settings
- WordPress hook integration with a structured API
- Composer-ready and lightweight
Frequently asked questions about Wp Steroids
- Is metabolism/wp-steroids a Laravel package or a WordPress plugin?
- It is a WordPress plugin, not a Laravel package. The brief frames it as Laravel/PHP, but the name and description point to a WordPress plugin that uses YAML configuration and Laravel-inspired architecture. It will not integrate with Laravel's service container, Eloquent, config pipeline, or console.
- How do I install WP Steroids with Composer?
- The Composer name is metabolism/wp-steroids, but the evaluation found no canonical repository and no confirmed Packagist or WPackagist listing. Verify the source and release artifacts before installing. If vetted, install it into your WordPress plugin or mu-plugins directory through your normal Composer or Bedrock pipeline and activate it in WordPress. Do not require it inside a Laravel application.
- What WordPress and PHP versions does WP Steroids support?
- The assessment describes the target runtime as WordPress 6.x and PHP 8.1+, but it found no evidence of a published compatibility matrix or testing against WordPress 6.x and PHP 8.3. Confirm supported WordPress versions, PHP versions, and multisite behavior from the source and release notes before adopting. Treat compatibility as unproven until you test it on a disposable WordPress instance.
- What WordPress features can I configure in YAML with WP Steroids?
- The package is described as replacing boilerplate PHP with declarative YAML, likely covering custom post types, taxonomies, meta fields, shortcodes, and hook wiring. The evaluation notes that the exact primitives it owns are a key open question. Confirm which features are supported and which are explicitly out of scope before mapping an existing site.
- Can I use WP Steroids inside a Laravel application?
- No, do not load WP Steroids inside a Laravel application. It is a WordPress plugin and does not integrate with Laravel's container, Eloquent, or config and console pipeline. It can only relate to Laravel indirectly through headless WordPress over REST or GraphQL, or via a bridge such as Corcel.
- Is WP Steroids safe to use in production?
- Treat it as unvetted until source review is complete. The evaluation flags an unknown canonical repository, a single maintainer, 23 stars, no visible downstream adopters, and a future-dated release timestamp. Pilot it on a greenfield, non-revenue WordPress site first and keep the legacy plugin set installed but inactive for one release cycle so you can roll back.
- Does WP Steroids validate YAML configuration and surface typos?
- The assessment warns that declarative schemas tend to accumulate undocumented keys and that without schema validation, typos can fail silently at runtime. It is unknown whether WP Steroids ships schema validation or how config errors are surfaced, fatal or silent. Review the config-loading code and test invalid YAML before relying on it. Also confirm YAML files are not web-accessible.
- How does WP Steroids handle YAML parsing and security?
- Config-driven plugins introduce a deserialization and config-injection surface. Confirm the parser, for example symfony/yaml with unsafe PARSE_* flags disabled, that YAML files are not publicly accessible, and that no dynamic callable or eval resolution occurs. The evaluation lists these as required source-review checks, not confirmed guarantees.
- Does WP Steroids support WordPress multisite and caching plugins?
- There is no evidence in the assessment of multisite support or conflict testing against common caching and SEO plugins. The evaluation explicitly asks for the supported matrix, including multisite, and for verification against object cache and full-page caching layers. Test these in a staging WordPress environment before production.
- Is WP Steroids actively maintained, and what are the alternatives?
- The assessment reports a single maintainer, bus factor 1, 23 stars, no visible downstream adopters, and metadata integrity concerns including an unknown repository and a future-dated release. That creates high abandonment risk; ask about tests, CI, SECURITY.md, versioning discipline, and a succession or fork plan. Alternatives include ACF Pro plus CPT UI and custom snippets, a custom lightweight plugin, or headless WordPress with Corcel for Laravel consumers.
Weaver
How can I help you explore Laravel packages today?