Hello! Just wanted to start off and say that I love the ambition of this project here. I understand that this project is still early; however, I certainly could have a use case for this crate. I have plans to potentially use this on AWS Lambda but I would like control over starting chromedriver and the browser session. (I dont use the installed version of chrome, I use the canaries or standalone test builds in a separate file location since aws lambda file system is read only). Would it be possible to group the patching logic into its own usability so that I and others can patch the chromedriver but then start chrome and chromedriver on our own?
Hello! Just wanted to start off and say that I love the ambition of this project here. I understand that this project is still early; however, I certainly could have a use case for this crate. I have plans to potentially use this on AWS Lambda but I would like control over starting chromedriver and the browser session. (I dont use the installed version of chrome, I use the canaries or standalone test builds in a separate file location since aws lambda file system is read only). Would it be possible to group the patching logic into its own usability so that I and others can patch the chromedriver but then start chrome and chromedriver on our own?