Weave Code
Framework Laravel Package
wpstarter/framework
WpStarter Framework brings Laravel-style development to WordPress: service container, routing, Eloquent ORM, Blade views, and migrations. Build plugins and themes with modern PHP architecture while staying fully compatible with WordPress.
The WpStarter Framework - Laravel Framework for WordPress
Frequently asked questions about Framework
- What is wpstarter/framework?
- WpStarter Framework is a Laravel-based framework layer that runs inside WordPress, so you can build plugins and themes with a service container, routing, Eloquent ORM, Blade views and migrations. It stays fully compatible with WordPress while giving your code modern PHP architecture instead of procedural hooks and scattered wp_* calls. The current 2.x line targets Laravel 12 on PHP 8.2 or newer.
- How do I install wpstarter/framework with Composer?
- Install it as a normal Composer package with composer require wpstarter/framework and pin the constraint you have actually validated, currently ^2.1.7. The framework bootstraps from inside WordPress, so the plugin or theme that loads it must be wired into the WordPress lifecycle. If production is still on the 1.x line, keep that constraint on production branches until your 2.x upgrade branch is green.
- Which PHP and Laravel versions does WpStarter Framework 2.x require?
- The 2.x baseline, established at v2.0.0 and still current at v2.1.7, requires Laravel 12 and PHP 8.2 or newer. No patch release in the 2.1.x line has changed that floor or added new required dependencies. Projects still on Laravel 10 or 11 must remain on the 1.x line until the host application is upgraded.
- Can I use Eloquent models instead of wp_* queries and WP_Query?
- Yes. WpStarter provides Eloquent ORM access plus typed bindings for WordPress core types such as WP_User|null and WPDB, so you can model and query data with Eloquent rather than hand-written SQL or wp_* helpers. You can still call wp_* functions where native WordPress behaviour is expected, mixing both through the container. Watch for type collisions at the boundary and scope declare(strict_types=1) to your own hybrid code.
- Can I use Blade templates in WordPress themes and plugins?
- Blade views are part of the package, so themes and plugins can render templates through the Blade compiler instead of raw PHP includes. You get layouts, components and the escaping conventions Laravel developers already expect. Make sure the Blade compile cache directory is writable in your WordPress environment before relying on it in production.
- How do database migrations work in WpStarter Framework?
- Migrations are supported, so schema changes live in versioned migration files rather than ad-hoc dbDelta calls spread across activation hooks. Run them as part of your deployment or plugin activation flow and keep them under source control. Because the framework shares the WordPress database, choose table names and prefixes deliberately to avoid colliding with core tables or other plugins.
- How do I upgrade from WpStarter Framework 1.x to 2.x?
- Treat it as a project, not a Composer bump. Pin wpstarter/framework to ^1.10 on production branches, upgrade the host application to Laravel 12 while still on 1.x, then cut over to ^2.1.7 on a branch that passes your full test suite. Run composer why-not audits and confirm every companion package supports Laravel 12 and Symfony 7 before scheduling the release window.
- Where is the changelog or upgrade guide for the 2.1.x releases?
- Release notes for the 2.1.x line are thin: v2.1.7 ships only a compare link (v2.1.6...v2.1.7) and there is no UPGRADE guide. Because 2.1.0 through 2.1.7 are undocumented, diff composer.json and the public API across v2.0.0...v2.1.7 yourself. Run PHPStan level 8 and enumerate any new config keys, published assets or container bindings introduced in the 2.1.x minor before you upgrade.
- Is WpStarter Framework production-ready, and what is the performance impact?
- WordPress's own bootstrap still dominates hybrid request time; Laravel 12's leaner skeleton is a small constant rather than a step change, so do not expect a performance win from the framework itself. The real production risk is blast radius, since a Laravel major upgrade and WordPress plugin compatibility testing share one release window. Validate your entire plugin stack on staging, keep strict typing scoped, and audit companion packages for Laravel 12 and Symfony 7 support first.
- How do I test a plugin built with WpStarter Framework?
- Because classes resolve through the service container, you can bind test doubles for WordPress services and typed dependencies such as WP_User|null and WPDB inside your test suite. Unit-test container-resolved classes in isolation and cover the WordPress-facing layer with integration tests against a real WordPress install. Adding static analysis such as PHPStan level 8 helps catch type collisions at the Laravel and WordPress boundary.
Weaver
How can I help you explore Laravel packages today?