@eliot-akira , thanks for this PR.

• If we merge php-wasm/node: Update express to newest version, and move it to devDependencies wordpress-playground#1218 , then adding express as a dependency will be required. 👍 .

If you pull the latest changes from trunk, the tests should pass.

OK, merged from trunk, ran npm install, and now the tests pass locally and in the CI.

I suppose this PR can be merged before the other one (WordPress/wordpress-playground#1218), since that removes the express dependency from @php-wasm/node.

As an aside, recently I'm integrating wp-now in a team project setup, to make onboarding new members simpler by replacing wp-env and Docker. So far it's working great, much faster to get started.

As an aside, recently I'm integrating wp-now in a team project setup, to make onboarding new members simpler by replacing wp-env and Docker. So far it's working great, much faster to get started.

@eliot-akira YAY! I'm so glad to hear that! Personally I've ran into some rough edges with modes and auto-mounting things and would love to make that optional and configurable via CLI options. But other than it did the trick on my end, too. I think you'd like Studio – @sejas could give you early access.

Studio looks cool! From the screenshot I imagine a desktop app for managing local WordPress sites powered by Playground. Curious to try it, I signed up for the waitlist.

I'm still solving a few things to completely replace wp-env with wp-now.

• The "mapping" feature of .wp-env.json, a declarative way to mount local folders to the virtual file system. Surely it can be achieved with blueprints, or a script that reads an existing env file and generates dynamic blueprint steps.
• Run PHPUnit tests using wp-now. Getting close but not there yet (ran into WASM error, something to do with Asyncify.handleSleep - will file an issue when I have a minimal reproducible example).

@eliot-akira for mapping, let's explore that in Blueprints v2:

WordPress/php-toolkit#46