Repository navigation
PHP feature parity #763
Description
Let's make sure that PHP.wasm works as stable and well as the native PHP
Crashes and error monitoring
- wp-now: environment crashes when I try to save post #416
- Expose PHP errors with JavaScript events #665
- [PHP] Use JSPI when available, fall back to Asyncify #1867
- Asyncify: Test all network functions and all ways to trigger a function call #273
- WooCommerce crash #967
- PHP crash message not logged #474
PHP extensions
- intl
- exif
- Support Xdebug #314
- Enable CURL in Playground Web #1935
- PHP SoapClient extension #1236
- Support XMLRPC PHP extension #628
- Error because of lack of cURL and allow_url_fopen #1008
- PHP: Support libwebp on PHP 7.0 – 7.3 #1381
- PHP Extension: add support for mbregex #815
- Draft: Support dynamic loading of PHP extensions via dlopen #673
Features
- Support popular PHP libraries and tools #766
- PHP: Implement TLS 1.2 to decrypt https:// and ssl:// traffic and translate it into fetch() #1926
$_FILES[...]['error']should beintand notstring#914- Breaking: Loopback Request Support #1287
- Stack Overflow: memory access out of bounds #816
- PHP: Make proc_open work without requiring an explicit sleep() #951
- Cannot set PHP temporary directory in CLI (sys_temp_dir) #828
- PHP: Don't throw ExitStatus 0 #479
- Support wp_mail() #276
- Support PHP 8.3 #820
- [PHP] Find a way to shutdown the WASM module and reclaim memory #287
- Prevent memory leaks on reinstantiation, open up cookies, fix compilation of php >=7.4 #639
Nice to haves
Not all issues with the PHP.wasm label made it here. That's intentional. Let's focus on the ones listed above.
Activity
[-]Tracking: Reach PHP.wasm stability and feature parity[/-][+]PHP.wasm stability and feature parity[/+][-]PHP.wasm stability and feature parity[/-][+]PHP feature parity[/+]