chrome-devtools-protocol
chrome-devtools-protocol copied to clipboard
Chrome Devtools Protocol client for PHP
Composer 2 autoloading errors occurs due to wrench package PSR-0 incompliance: see: https://github.com/varspool/Wrench/issues/133 Package seems to be abandoned, solution can be to use a fork. https://github.com/chrome-php/wrench is mentioned there.
The commit changes HTTP methods from POST to GET. As we can see in the Chrome DevTools Protocol document. the endpoints are defined as follow. - GET /json/version - GET...
- the launcher, `launchWithExecutable` method looks for Guzzle `ConnectException` and catches in that infinite loop - currently, on my machines, Guzzle is throwing explicit `RequestException` so Launcher always fails immediately...
I would be nice if this package could also work with Guzzle 7. `^6.3|^7.0` [Guzzle 7 Upgrade Guide](https://github.com/guzzle/guzzle/blob/7.0.0/UPGRADING.md#60-to-70)
Fixes https://github.com/jakubkulhan/chrome-devtools-protocol/issues/37 I am not sure how to update the CI or if I did the PR correctly, please advise on anything missing or wrong.
The latest version of PHP is 8.1 and this package does not support it. I forced it to install to see if it would work, but seems that at least...
We can pass port 0 directly to chrome and it will use available port automatically and prints the chosen one to stderr as mentioned in docs: https://chromedevtools.github.io/devtools-protocol/#:~:text=how%20do%20i%20access%20the%20browser%20target%3F
Fix/php8
Primary changes: * Set php >=7.1 to allow for php 8.0 * Crossgrade to php-parallel-lint/php-parallel-lint * Upgrade phpstan * Enable phpunit v9 Notes: * phpunit and lint are passing *...
Wrench\Client keeps all received Payload objects in perpetuity. This results in a script eventually running out of memory if it's reading a large stream of data. Instead, after receiving any...
If there's an issue that closes the WebSocket connection, it's not longer possible to cleanly close the session. If you call Session::close() on the session object after an issue that...