Garris
@benbcai thank you for explaining. Please let me know if you can get this sorted out. I am happy to bump BackstopJS when the package version is published to npm.
Great! Will do this soon -- thank you @mirzazeyrek.
Hi @saitho -- the `engineOptions` props are pretty much passed directly into puppeteer... https://github.com/garris/BackstopJS/blob/9fa768b3444cee66e427dd68dab0cb6dffe2dda1/core/util/runPuppet.js#L61  For more information about how this can be used you can look at Puppeteer documentation.
@saitho Does this new config option mean that we do not need this hack anymore? https://github.com/garris/BackstopJS/pull/1374/commits/e3a80e207088316aa03fcaf70e9322b51a0ec335
@klodoma yes, I am supportive. Others have asked for this as well. It could be as simple as an operation which runs after the current reporting flow completes and copies...
I like `keepReports` -- but maybe `archiveReports` is a little more accurate (cause we would literally be creating self-contained report archives.)
I believe this was fixed in 5.3.0... https://github.com/garris/BackstopJS/issues/1291#issuecomment-807972839
@onigoetz thanks for checking in! I pushed version 2 to master and then NPM@latest weeks ago. Since then I've had to work out a few critical windows issues, try to...
@onigoetz Tags are updated!
Omg — panting — out of breath — so busy... you guys know I this for free right? halp! 🤪💜✨