{"id":13828366,"url":"https://github.com/reactphp/child-process","last_synced_at":"2025-05-15T16:05:42.566Z","repository":{"id":15963154,"uuid":"18705801","full_name":"reactphp/child-process","owner":"reactphp","description":"Event-driven library for executing child processes with ReactPHP.","archived":false,"fork":false,"pushed_at":"2025-01-01T16:40:31.000Z","size":198,"stargazers_count":324,"open_issues_count":5,"forks_count":47,"subscribers_count":16,"default_branch":"0.7.x","last_synced_at":"2025-05-14T03:34:31.001Z","etag":null,"topics":["child-process","php","reactphp"],"latest_commit_sha":null,"homepage":"https://reactphp.org/child-process/","language":"PHP","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/reactphp.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null},"funding":{"github":["reactphp","clue","WyriHaximus"],"open_collective":"reactphp"}},"created_at":"2014-04-12T14:23:29.000Z","updated_at":"2025-05-11T01:21:48.000Z","dependencies_parsed_at":"2024-01-15T22:42:59.113Z","dependency_job_id":"b55fb4d5-60f0-459c-9609-5e1bb01bffdc","html_url":"https://github.com/reactphp/child-process","commit_stats":{"total_commits":130,"total_committers":17,"mean_commits":7.647058823529412,"dds":0.6230769230769231,"last_synced_commit":"bdc37c797030315a2ba7664010cc7d433c279dba"},"previous_names":[],"tags_count":15,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactphp%2Fchild-process","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactphp%2Fchild-process/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactphp%2Fchild-process/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactphp%2Fchild-process/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/reactphp","download_url":"https://codeload.github.com/reactphp/child-process/tar.gz/refs/heads/0.7.x","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254374427,"owners_count":22060611,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["child-process","php","reactphp"],"created_at":"2024-08-04T09:02:43.335Z","updated_at":"2025-05-15T16:05:42.544Z","avatar_url":"https://github.com/reactphp.png","language":"PHP","funding_links":["https://github.com/sponsors/reactphp","https://github.com/sponsors/clue","https://github.com/sponsors/WyriHaximus","https://opencollective.com/reactphp"],"categories":["PHP"],"sub_categories":[],"readme":"# ChildProcess\n\n[![CI status](https://github.com/reactphp/child-process/actions/workflows/ci.yml/badge.svg)](https://github.com/reactphp/child-process/actions)\n[![installs on Packagist](https://img.shields.io/packagist/dt/react/child-process?color=blue\u0026label=installs%20on%20Packagist)](https://packagist.org/packages/react/child-process)\n\nEvent-driven library for executing child processes with\n[ReactPHP](https://reactphp.org/).\n\n\u003e **Development version:** This branch contains the code for the upcoming 0.7 release.\n\u003e For the code of the current stable 0.6.x release, check out the\n\u003e [`0.6.x` branch](https://github.com/reactphp/child-process/tree/0.6.x).\n\u003e\n\u003e The upcoming 0.7 release will be the way forward for this package.\n\u003e However, we will still actively support 0.6.x for those not yet\n\u003e on the latest version.\n\u003e See also [installation instructions](#install) for more details.\n\nThis library integrates [Program Execution](http://php.net/manual/en/book.exec.php)\nwith the [EventLoop](https://github.com/reactphp/event-loop).\nChild processes launched may be signaled and will emit an\n`exit` event upon termination.\nAdditionally, process I/O streams (i.e. STDIN, STDOUT, STDERR) are exposed\nas [Streams](https://github.com/reactphp/stream).\n\n**Table of contents**\n\n* [Quickstart example](#quickstart-example)\n* [Process](#process)\n  * [Stream Properties](#stream-properties)\n  * [Command](#command)\n  * [Termination](#termination)\n  * [Custom pipes](#custom-pipes)\n  * [Windows Compatibility](#windows-compatibility)\n* [Install](#install)\n* [Tests](#tests)\n* [License](#license)\n\n## Quickstart example\n\n```php\n$process = new React\\ChildProcess\\Process('echo foo');\n$process-\u003estart();\n\n$process-\u003estdout-\u003eon('data', function ($chunk) {\n    echo $chunk;\n});\n\n$process-\u003eon('exit', function($exitCode, $termSignal) {\n    echo 'Process exited with code ' . $exitCode . PHP_EOL;\n});\n```\n\nSee also the [examples](examples).\n\n## Process\n\n### Stream Properties\n\nOnce a process is started, its I/O streams will be constructed as instances of\n`React\\Stream\\ReadableStreamInterface` and `React\\Stream\\WritableStreamInterface`. \nBefore `start()` is called, these properties are not set. Once a process terminates, \nthe streams will become closed but not unset.\n\nFollowing common Unix conventions, this library will start each child process\nwith the three pipes matching the standard I/O streams as given below by default.\nYou can use the named references for common use cases or access these as an\narray with all three pipes.\n\n* `$stdin`  or `$pipes[0]` is a `WritableStreamInterface`\n* `$stdout` or `$pipes[1]` is a `ReadableStreamInterface`\n* `$stderr` or `$pipes[2]` is a `ReadableStreamInterface`\n\nNote that this default configuration may be overridden by explicitly passing\n[custom pipes](#custom-pipes), in which case they may not be set or be assigned\ndifferent values. In particular, note that [Windows support](#windows-compatibility)\nis limited in that it doesn't support non-blocking STDIO pipes. The `$pipes`\narray will always contain references to all pipes as configured and the standard\nI/O references will always be set to reference the pipes matching the above\nconventions. See [custom pipes](#custom-pipes) for more details.\n\nBecause each of these implement the underlying\n[`ReadableStreamInterface`](https://github.com/reactphp/stream#readablestreaminterface) or \n[`WritableStreamInterface`](https://github.com/reactphp/stream#writablestreaminterface), \nyou can use any of their events and methods as usual:\n\n```php\n$process = new Process($command);\n$process-\u003estart();\n\n$process-\u003estdout-\u003eon('data', function ($chunk) {\n    echo $chunk;\n});\n\n$process-\u003estdout-\u003eon('end', function () {\n    echo 'ended';\n});\n\n$process-\u003estdout-\u003eon('error', function (Exception $e) {\n    echo 'error: ' . $e-\u003egetMessage();\n});\n\n$process-\u003estdout-\u003eon('close', function () {\n    echo 'closed';\n});\n\n$process-\u003estdin-\u003ewrite($data);\n$process-\u003estdin-\u003eend($data = null);\n// …\n```\n\nFor more details, see the\n[`ReadableStreamInterface`](https://github.com/reactphp/stream#readablestreaminterface) and \n[`WritableStreamInterface`](https://github.com/reactphp/stream#writablestreaminterface).\n\n### Command\n\nThe `Process` class allows you to pass any kind of command line string:\n\n```php\n$process = new Process('echo test');\n$process-\u003estart();\n```\n\nThe command line string usually consists of a whitespace-separated list with\nyour main executable bin and any number of arguments. Special care should be\ntaken to escape or quote any arguments, escpecially if you pass any user input\nalong. Likewise, keep in mind that especially on Windows, it is rather common to\nhave path names containing spaces and other special characters. If you want to\nrun a binary like this, you will have to ensure this is quoted as a single\nargument using `escapeshellarg()` like this:\n\n```php\n$bin = 'C:\\\\Program files (x86)\\\\PHP\\\\php.exe';\n$file = 'C:\\\\Users\\\\me\\\\Desktop\\\\Application\\\\main.php';\n\n$process = new Process(escapeshellarg($bin) . ' ' . escapeshellarg($file));\n$process-\u003estart();\n```\n\nBy default, PHP will launch processes by wrapping the given command line string\nin a `sh` command on Unix, so that the first example will actually execute\n`sh -c echo test` under the hood on Unix. On Windows, it will not launch\nprocesses by wrapping them in a shell.\n\nThis is a very useful feature because it does not only allow you to pass single\ncommands, but actually allows you to pass any kind of shell command line and\nlaunch multiple sub-commands using command chains (with `\u0026\u0026`, `||`, `;` and\nothers) and allows you to redirect STDIO streams (with `2\u003e\u00261` and family).\nThis can be used to pass complete command lines and receive the resulting STDIO\nstreams from the wrapping shell command like this:\n\n```php\n$process = new Process('echo run \u0026\u0026 demo || echo failed');\n$process-\u003estart();\n```\n\n\u003e Note that [Windows support](#windows-compatibility) is limited in that it\n  doesn't support STDIO streams at all and also that processes will not be run\n  in a wrapping shell by default. If you want to run a shell built-in function\n  such as `echo hello` or `sleep 10`, you may have to prefix your command line\n  with an explicit shell like `cmd /c echo hello`.\n\nIn other words, the underlying shell is responsible for managing this command\nline and launching the individual sub-commands and connecting their STDIO\nstreams as appropriate.\nThis implies that the `Process` class will only receive the resulting STDIO\nstreams from the wrapping shell, which will thus contain the complete\ninput/output with no way to discern the input/output of single sub-commands.\n\nIf you want to discern the output of single sub-commands, you may want to\nimplement some higher-level protocol logic, such as printing an explicit\nboundary between each sub-command like this:\n\n```php\n$process = new Process('cat first \u0026\u0026 echo --- \u0026\u0026 cat second');\n$process-\u003estart();\n```\n\nAs an alternative, considering launching one process at a time and listening on\nits `exit` event to conditionally start the next process in the chain.\nThis will give you an opportunity to configure the subsequent process I/O streams:\n\n```php\n$first = new Process('cat first');\n$first-\u003estart();\n\n$first-\u003eon('exit', function () {\n    $second = new Process('cat second');\n    $second-\u003estart();\n});\n```\n\nKeep in mind that PHP uses the shell wrapper for ALL command lines on Unix.\nWhile this may seem reasonable for more complex command lines, this actually\nalso applies to running the most simple single command:\n\n```php\n$process = new Process('yes');\n$process-\u003estart();\n```\n\nThis will actually spawn a command hierarchy similar to this on Unix:\n\n```\n5480 … \\_ php example.php\n5481 …    \\_ sh -c yes\n5482 …        \\_ yes\n```\n\nThis means that trying to get the underlying process PID or sending signals\nwill actually target the wrapping shell, which may not be the desired result\nin many cases.\n\nIf you do not want this wrapping shell process to show up, you can simply\nprepend the command string with `exec` on Unix platforms, which will cause the\nwrapping shell process to be replaced by our process:\n\n```php\n$process = new Process('exec yes');\n$process-\u003estart();\n```\n\nThis will show a resulting command hierarchy similar to this:\n\n```\n5480 … \\_ php example.php\n5481 …    \\_ yes\n```\n\nThis means that trying to get the underlying process PID and sending signals\nwill now target the actual command as expected.\n\nNote that in this case, the command line will not be run in a wrapping shell.\nThis implies that when using `exec`, there's no way to pass command lines such\nas those containing command chains or redirected STDIO streams.\n\nAs a rule of thumb, most commands will likely run just fine with the wrapping\nshell.\nIf you pass a complete command line (or are unsure), you SHOULD most likely keep\nthe wrapping shell.\nIf you're running on Unix and you want to pass an invidual command only, you MAY\nwant to consider prepending the command string with `exec` to avoid the wrapping shell.\n\n### Termination\n\nThe `exit` event will be emitted whenever the process is no longer running.\nEvent listeners will receive the exit code and termination signal as two\narguments:\n\n```php\n$process = new Process('sleep 10');\n$process-\u003estart();\n\n$process-\u003eon('exit', function ($code, $term) {\n    if ($term === null) {\n        echo 'exit with code ' . $code . PHP_EOL;\n    } else {\n        echo 'terminated with signal ' . $term . PHP_EOL;\n    }\n});\n```\n\nNote that `$code` is `null` if the process has terminated, but the exit\ncode could not be determined.\nSimilarly, `$term` is `null` unless the process has terminated in response to\nan uncaught signal sent to it.\nThis is not a limitation of this project, but actual how exit codes and signals\nare exposed on POSIX systems, for more details see also\n[here](https://unix.stackexchange.com/questions/99112/default-exit-code-when-process-is-terminated).\n\nIt's also worth noting that process termination depends on all file descriptors\nbeing closed beforehand.\nThis means that all [process pipes](#stream-properties) will emit a `close`\nevent before the `exit` event and that no more `data` events will arrive after\nthe `exit` event.\nAccordingly, if either of these pipes is in a paused state (`pause()` method\nor internally due to a `pipe()` call), this detection may not trigger.\n\nThe `terminate(?int $signal = null): bool` method can be used to send the\nprocess a signal (SIGTERM by default).\nDepending on which signal you send to the process and whether it has a signal\nhandler registered, this can be used to either merely signal a process or even\nforcefully terminate it.\n\n```php\n$process-\u003eterminate(SIGUSR1);\n```\n\nKeep the above section in mind if you want to forcefully terminate a process.\nIf your process spawn sub-processes or implicitly uses the\n[wrapping shell mentioned above](#command), its file descriptors may be\ninherited to child processes and terminating the main process may not\nnecessarily terminate the whole process tree.\nIt is highly suggested that you explicitly `close()` all process pipes\naccordingly when terminating a process:\n\n```php\n$process = new Process('sleep 10');\n$process-\u003estart();\n\nLoop::addTimer(2.0, function () use ($process) {\n    foreach ($process-\u003epipes as $pipe) {\n        $pipe-\u003eclose();\n    }\n    $process-\u003eterminate();\n});\n```\n\nFor many simple programs these seamingly complicated steps can also be avoided\nby prefixing the command line with `exec` to avoid the wrapping shell and its\ninherited process pipes as [mentioned above](#command).\n\n```php\n$process = new Process('exec sleep 10');\n$process-\u003estart();\n\nLoop::addTimer(2.0, function () use ($process) {\n    $process-\u003eterminate();\n});\n```\n\nMany command line programs also wait for data on `STDIN` and terminate cleanly\nwhen this pipe is closed.\nFor example, the following can be used to \"soft-close\" a `cat` process:\n\n```php\n$process = new Process('cat');\n$process-\u003estart();\n\nLoop::addTimer(2.0, function () use ($process) {\n    $process-\u003estdin-\u003eend();\n});\n```\n\nWhile process pipes and termination may seem confusing to newcomers, the above\nproperties actually allow some fine grained control over process termination,\nsuch as first trying a soft-close and then applying a force-close after a\ntimeout.\n\n### Custom pipes\n\nFollowing common Unix conventions, this library will start each child process\nwith the three pipes matching the standard I/O streams by default. For more\nadvanced use cases it may be useful to pass in custom pipes, such as explicitly\npassing additional file descriptors (FDs) or overriding default process pipes.\n\nNote that passing custom pipes is considered advanced usage and requires a\nmore in-depth understanding of Unix file descriptors and how they are inherited\nto child processes and shared in multi-processing applications.\n\nIf you do not want to use the default standard I/O pipes, you can explicitly\npass an array containing the file descriptor specification to the constructor\nlike this:\n\n```php\n$fds = array(\n    // standard I/O pipes for stdin/stdout/stderr\n    0 =\u003e array('pipe', 'r'),\n    1 =\u003e array('pipe', 'w'),\n    2 =\u003e array('pipe', 'w'),\n\n    // example FDs for files or open resources\n    4 =\u003e array('file', '/dev/null', 'r'),\n    6 =\u003e fopen('log.txt','a'),\n    8 =\u003e STDERR,\n\n    // example FDs for sockets\n    10 =\u003e fsockopen('localhost', 8080),\n    12 =\u003e stream_socket_server('tcp://0.0.0.0:4711')\n);\n\n$process = new Process($cmd, null, null, $fds);\n$process-\u003estart();\n```\n\nUnless your use case has special requirements that demand otherwise, you're\nhighly recommended to (at least) pass in the standard I/O pipes as given above.\nThe file descriptor specification accepts arguments in the exact same format\nas the underlying [`proc_open()`](http://php.net/proc_open) function.\n\nOnce the process is started, the `$pipes` array will always contain references to\nall pipes as configured and the standard I/O references will always be set to\nreference the pipes matching common Unix conventions. This library supports any\nnumber of pipes and additional file descriptors, but many common applications\nbeing run as a child process will expect that the parent process properly\nassigns these file descriptors.\n\n### Windows Compatibility\n\nDue to platform constraints, this library provides only limited support for\nspawning child processes on Windows. In particular, PHP does not allow accessing\nstandard I/O pipes on Windows without blocking. As such, this project will not\nallow constructing a child process with the default process pipes and will\ninstead throw a `LogicException` on Windows by default:\n\n```php\n// throws LogicException on Windows\n$process = new Process('ping example.com');\n$process-\u003estart();\n```\n\nThere are a number of alternatives and workarounds as detailed below if you want\nto run a child process on Windows, each with its own set of pros and cons:\n\n*   As of PHP 8, you can start the child process with `socket` pair descriptors\n    in place of normal standard I/O pipes like this:\n\n    ```php\n    $process = new Process(\n        'ping example.com',\n        null,\n        null,\n        [\n            ['socket'],\n            ['socket'],\n            ['socket']\n        ]\n    );\n    $process-\u003estart();\n\n    $process-\u003estdout-\u003eon('data', function ($chunk) {\n        echo $chunk;\n    });\n    ```\n\n    These `socket` pairs support non-blocking process I/O on any platform,\n    including Windows. However, not all programs accept stdio sockets.\n\n*   This package does work on\n    [`Windows Subsystem for Linux`](https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux)\n    (or WSL) without issues. When you are in control over how your application is\n    deployed, we recommend [installing WSL](https://msdn.microsoft.com/en-us/commandline/wsl/install_guide)\n    when you want to run this package on Windows.\n\n*   If you only care about the exit code of a child process to check if its\n    execution was successful, you can use [custom pipes](#custom-pipes) to omit\n    any standard I/O pipes like this:\n\n    ```php\n    $process = new Process('ping example.com', null, null, array());\n    $process-\u003estart();\n\n    $process-\u003eon('exit', function ($exitcode) {\n        echo 'exit with ' . $exitcode . PHP_EOL;\n    });\n    ```\n\n    Similarly, this is also useful if your child process communicates over\n    sockets with remote servers or even your parent process using the\n    [Socket component](https://github.com/reactphp/socket). This is usually\n    considered the best alternative if you have control over how your child\n    process communicates with the parent process.\n\n*   If you only care about command output after the child process has been\n    executed, you can use [custom pipes](#custom-pipes) to configure file\n    handles to be passed to the child process instead of pipes like this:\n\n    ```php\n    $process = new Process('ping example.com', null, null, array(\n        array('file', 'nul', 'r'),\n        $stdout = tmpfile(),\n        array('file', 'nul', 'w')\n    ));\n    $process-\u003estart();\n\n    $process-\u003eon('exit', function ($exitcode) use ($stdout) {\n        echo 'exit with ' . $exitcode . PHP_EOL;\n\n        // rewind to start and then read full file (demo only, this is blocking).\n        // reading from shared file is only safe if you have some synchronization in place\n        // or after the child process has terminated.\n        rewind($stdout);\n        echo stream_get_contents($stdout);\n        fclose($stdout);\n    });\n    ```\n\n    Note that this example uses `tmpfile()`/`fopen()` for illustration purposes only.\n    This should not be used in a truly async program because the filesystem is\n    inherently blocking and each call could potentially take several seconds.\n    See also the [Filesystem component](https://github.com/reactphp/filesystem) as an\n    alternative.\n\n*   If you want to access command output as it happens in a streaming fashion,\n    you can use redirection to spawn an additional process to forward your\n    standard I/O streams to a socket and use [custom pipes](#custom-pipes) to\n    omit any actual standard I/O pipes like this:\n\n    ```php\n    $server = new React\\Socket\\Server('127.0.0.1:0');\n    $server-\u003eon('connection', function (React\\Socket\\ConnectionInterface $connection) {\n        $connection-\u003eon('data', function ($chunk) {\n            echo $chunk;\n        });\n    });\n\n    $command = 'ping example.com | foobar ' . escapeshellarg($server-\u003egetAddress());\n    $process = new Process($command, null, null, array());\n    $process-\u003estart();\n\n    $process-\u003eon('exit', function ($exitcode) use ($server) {\n        $server-\u003eclose();\n        echo 'exit with ' . $exitcode . PHP_EOL;\n    });\n    ```\n\n    Note how this will spawn another fictional `foobar` helper program to consume\n    the standard output from the actual child process. This is in fact similar\n    to the above recommendation of using socket connections in the child process,\n    but in this case does not require modification of the actual child process.\n\n    In this example, the fictional `foobar` helper program can be implemented by\n    simply consuming all data from standard input and forwarding it to a socket\n    connection like this:\n\n    ```php\n    $socket = stream_socket_client($argv[1]);\n    do {\n        fwrite($socket, $data = fread(STDIN, 8192));\n    } while (isset($data[0]));\n    ```\n\n    Accordingly, this example can also be run with plain PHP without having to\n    rely on any external helper program like this:\n\n    ```php\n    $code = '$s=stream_socket_client($argv[1]);do{fwrite($s,$d=fread(STDIN, 8192));}while(isset($d[0]));';\n    $command = 'ping example.com | php -r ' . escapeshellarg($code) . ' ' . escapeshellarg($server-\u003egetAddress());\n    $process = new Process($command, null, null, array());\n    $process-\u003estart();\n    ```\n\n    See also [example #23](examples/23-forward-socket.php).\n\n    Note that this is for illustration purposes only and you may want to implement\n    some proper error checks and/or socket verification in actual production use\n    if you do not want to risk other processes connecting to the server socket.\n    In this case, we suggest looking at the excellent\n    [createprocess-windows](https://github.com/cubiclesoft/createprocess-windows).\n\nAdditionally, note that the [command](#command) given to the `Process` will be\npassed to the underlying Windows-API\n([`CreateProcess`](https://docs.microsoft.com/en-us/windows/desktop/api/processthreadsapi/nf-processthreadsapi-createprocessa))\nas-is and the process will not be launched in a wrapping shell by default. In\nparticular, this means that shell built-in functions such as `echo hello` or\n`sleep 10` may have to be prefixed with an explicit shell command like this:\n\n```php\n$process = new Process('cmd /c echo hello', null, null, $pipes);\n$process-\u003estart();\n```\n\n## Install\n\nThe recommended way to install this library is [through Composer](https://getcomposer.org/).\n[New to Composer?](https://getcomposer.org/doc/00-intro.md)\n\nOnce released, this project will follow [SemVer](https://semver.org/).\nAt the moment, this will install the latest development version:\n\n```bash\ncomposer require react/child-process:^0.7@dev\n```\n\nSee also the [CHANGELOG](CHANGELOG.md) for details about version upgrades.\n\nThis project aims to run on any platform and thus does not require any PHP\nextensions and supports running on legacy PHP 5.3 through current PHP 8+ and HHVM.\nIt's *highly recommended to use the latest supported PHP version* for this project.\n\nNote that legacy platforms that use PHP compiled with the legacy `--enable-sigchild`\noption may not reliably determine the child process' exit code in some cases.\nThis should not affect most installations as this configure option is not used\nby default and most distributions (such as Debian and Ubuntu) are known to not\nuse this by default. This option may be used on some  installations that use\n[Oracle OCI8](https://www.php.net/manual/en/book.oci8.php), see `phpinfo()` output\nto check if your installation might be affected.\n\nSee above note for limited [Windows Compatibility](#windows-compatibility).\n\n## Tests\n\nTo run the test suite, you first need to clone this repo and then install all\ndependencies [through Composer](https://getcomposer.org/):\n\n```bash\ncomposer install\n```\n\nTo run the test suite, go to the project root and run:\n\n```bash\nvendor/bin/phpunit\n```\n\n## License\n\nMIT, see [LICENSE file](LICENSE).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Freactphp%2Fchild-process","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Freactphp%2Fchild-process","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Freactphp%2Fchild-process/lists"}