WordPress Core just introduced an experimental feature that might finally kill the “Docker networking issue” nightmare for local development. By integrating the wp-env Playground runtime, we can now spin up a full WordPress environment without even having Docker installed on our machines.
I’ve been using wp-env since its inception. While it’s great for consistency, Docker is heavy. Furthermore, if you’re on a machine with limited RAM or just doing a quick refactor session, Docker feels like using a sledgehammer to crack a nut. This new runtime changes that.
Zero Docker, Full WordPress: The npx Command
To try it out, you don’t need to refactor your existing setup. You just need Node.js and a single command. Specifically, if you have an existing .wp-env.json, it will likely work out of the box with the new flag.
npx @wordpress/env start --runtime=playgroundThis command leverages WebAssembly (WASM) via WordPress Playground to run PHP and SQLite directly in your Node environment. Consequently, startup times drop from minutes to seconds.
Why the wp-env Playground Runtime Matters
For most of us, the primary bottleneck in local development isn’t the code—it’s the environment orchestration. The wp-env Playground runtime offers several pragmatic benefits for modern workflows:
- Zero Installation: No Docker Desktop, no WSL2 configuration headaches; if you have Node.js, you’re ready.
- Resource Efficiency: It runs lean, making it perfect for CI/CD pipelines where container overhead is expensive.
- Portability: It works everywhere Node.js runs, including Linux, macOS, and Windows.
However, there’s a significant gotcha. Because this uses the Playground architecture, it swaps MySQL for SQLite. While WordPress Core handles this gracefully now, some legacy plugins that write direct SQL queries might break. Therefore, treat this as a testing tool rather than a staging mirror.
Current Limitations of the Playground Runtime
We need to be clear: this is still experimental. In my testing, I found a few constraints that will keep me on Docker for complex projects. For instance, zip archive themes are not supported yet—only local directories or Git repositories work.
If you’re testing performance on high-end integrations, like we do with the WP-Bench AI Benchmark, the ephemeral nature of Playground might skew your results compared to a real-world server stack. Furthermore, support for PHP 7.2 and 7.3 has been dropped entirely in this runtime.
Configuring Your Environment
You can still use your standard configuration file. The runtime is simply a flag you pass to the start command. Here is a typical .wp-env.json setup that works with both Docker and the wp-env Playground runtime:
{
"core": "WordPress/WordPress#6.8",
"plugins": ["./my-custom-plugin"],
"themes": ["./my-custom-theme"],
"phpVersion": "8.2"
}Look, if this wp-env Playground runtime stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
Final Takeaway
The wp-env Playground runtime isn’t a replacement for Docker—not yet. But for rapid prototyping, quick refactoring sessions, and automated testing, it’s a massive step forward. Stop fighting your local environment and start shipping code. You can find more details in the official wp-env documentation and the WordPress Playground resources.
