Fix timeout starting sites with XDebug enabled using the packaged app

[epeicher]

Related issues

Related to STU-1183
Fix also suggested to the affected package WordPress/wordpress-playground#3125

Proposed Changes

• Apply a patch to @php-wasm/node to fix the timeout when starting sites with XDebug enabled using the packaged app.

Testing Instructions

1. Checkout this branch
2. Run cd cli and npm install to install CLI dependencies
3. Verify that the @php-wasm patch is applied, the following should be logged to the terminal:

Applying patches...
@php-wasm/node@3.0.22 ✔

4. Run cd .., delete node_modules so the previous patch is applied.
5. Run npm install to install main deps
6. Run npm start
7. Enable "Xdebug Support" beta feature in Settings → Beta Features
8. Open Edit Site Details for any site
9. Check "Enable Xdebug" checkbox and save
10. Verify that the site can be stopped and started successfully
11. Close Studio
12. Run npm run make to package the application
13. Once completed, open the out folder in the root of the repo, open your platform folder (e.g. Studio-darwin-arm64) and run Studio.app
14. Check that the site with Xdebug enabled starts successfully
15. Verify that the site can be stopped and started successfully

Test debugging in IDE

Copied from the original PR #2242

I used PhpStorm:

1. Create a site
2. Enable Xdebug and start the site
3. Open the site in PhpStorm
4. To stop breaking at the first line in PHPStorm, open Settings > PHP > Debug > Xdebug:
   • Disable > Force break at first line when no path mapping specified
   • Disable > Force break at first line when a script is outside the project
5. Open WP Admin using link in Studio
6. In PhpStorm, open the path mapping notification (or navigate to PHP|Servers) and configure mapping for your site's server:

• Host: localhost:8884
• Port: 80
• File directory: /Users/USERNAME/Studio/SITEDIR
• Absolute path on the server: /wordpress

16. Add a breakpoint somewhere, e.g. in wp-config.php file
17. Refresh WP Admin
18. Confirm PhpStorm stops execution on the breakpoint

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[wojtekn]

I'm testing it now.

[wojtekn]

It works as expected now.

[sejas]

I think we shouldn’t remove this error that is thrown when the PHP version isn’t supported.

[epeicher]

Well spotted! I think that was removed by mistake. I'll add it back

[epeicher]

I updated this patch as part of #2416

[sejas]

I followed the test instructions and confirm the npm install applied the patch and I was able to start and stop a site with Xdebug:

Applying patches...
@php-wasm/node@3.0.22 ✔
pm2@6.0.14 ✔
ps-man@1.1.8 ✔

I just noticed that we are removing the error when the PHP version is not supported. throw new Error(`Unsupported PHP version ${version}`);. I suggest adding it back or explaining why that's necessary in .js and not in .cjs

[epeicher]

I just noticed that we are removing the error when the PHP version is not supported. throw new Error(Unsupported PHP version ${version});. I suggest adding it back or explaining why that's necessary in .js and not in .cjs

That was a great catch @sejas! For some reason, my IDE is deleting that line when updating the file, but I have managed to add it back, as it is unrelated to the patch. The updated patch can be found in #2416