deno-puppeteer
deno-puppeteer copied to clipboard
Question: what is the strategy of keeping this fork repo in sync with the forked repo?
Currently it appears this repo is based on the 16.2.0 version of Puppeteer. Puppeteer has seen changes since, and is currently at version: 18.2.1
Is there a strategy to keep the Node and Deno versions in sync? Or was this fork just meant as a kind of experiment?
I see the author is not active on this repo recently, there is open PRs that are not reviewed. Hope he still take care the repo.
+1 on this question!
@lucacasonato With some guidance, I could invest some time to update it from time to time.
If anyone is open to collaborating, I'm considering forking this repo as it seems to be unmaintained.