Loosen version constraint for childprocess dependency#40
Loosen version constraint for childprocess dependency#40cjlarose wants to merge 1 commit intobrowserup:masterfrom
Conversation
|
@cjlarose did you gave up on this gem?I'm facing this childprocess conflict as well and unfortunately looks like this gem is unmaintained 😞 |
|
I was able to just use my fork (https://github.com/cjlarose/browsermob-proxy-rb) directly from github (branch: But ultimately, I ended up using a different solution to my problem altogether. Originally, I wanted to capture network traffic as a HAR when running my automated test suite. Browsermob proxy / Browserup proxy seemed like a good option, but ultimately, I went with a solution that connects to the browser (Chrome in this case) using See https://github.com/Everettss/puppeteer-har I wrote a HTTP interface around that library so I could use it from Ruby |
I have an application that uses
childprocess (= 3.0.0). Trying to introducebrowsermob-proxy-rb (~> 0.3.1)to that project produces a conflict becausebrowsermob-proxy-rbdeclares a dependency onchildprocess (~> 0.5). To resolve the conflict, I can downgradechildprocess, but I'd prefer not to. This project appears to be compatible with all versions ofchildprocessfrom 0.5 to 3.0.0, so this change just loosens the version constraint in thegemspec.If I remove the constraint in my
Gemfilethat I want the latest version ofbrowsermob-proxy-rb,bundlerinstalls version 0.1.7 since that version had no constraint at all on thechildprocessversion. This is similarly undesirable.browsermob-proxy-rb/browsermob-proxy.gemspec
Line 19 in aa7e41f