Yannick Decat
Yannick Decat
@Nielsvanpach, this will be completed today.
@Nielsvanpach I made a PR #1834 for this issue 4 months ago. It had been recently closed by spatie-bot. I guess this issue should maybe be reopened ?
@adamziel I'm currently trying to run the `composer` PHAR file in `php-wasm/web`, but I'm encountering the following stack trace when running `php.cli( [ 'php', 'composer.phar', 'install' ] );`: ``` Uncaught...
@adamziel I made a mistake. I solved it and here is what returns `php-wasm/web` when I run `php.cli( [ 'php', 'composer.phar', 'install' ] )` now : With [#1093]...
In my quest to correct the errors above I found out other elements to add into the `Asyncify` functions list : ``` "Curl_proxy_connect",\ "call_extract_if_dead",\ "Curl_conncache_foreach",\ ``` Should I update the...
@adamziel done 👌
@adamziel My apologies. The conflicts have been resolved. But `test-e2e` and `build` failed?
I successfully tested compiling `php-wasm/web/kitchen-sink` with `WITH_CURL` and `WITH_CLI_SAPI`, and it indeed makes `php.cli()` work properly. I suppose this is probably related to [#1039] and this is only a matter...
I take this "issue" to go further : In my quest to make the composer phar file work. I made the use of the [php proxy server](https://github.com/WordPress/wordpress-playground/pull/1546) on `127.0.0.1:5263` port...
I decided to go further on making composer phar work. I modified the current proxy server to run without the use of `php -S` because of additional Headers added everytime...