Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: what is the strategy of keeping this fork repo in sync with the forked repo? #64

Open
jeroendee opened this issue Oct 12, 2022 · 3 comments

Comments

@jeroendee
Copy link

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?

@jeroendee jeroendee changed the title Question: what is the strategy in keeping this fork repo in sync with the forked repo? Question: what is the strategy of keeping this fork repo in sync with the forked repo? Oct 12, 2022
@cavoirom
Copy link

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.

@wvbe
Copy link

wvbe commented Mar 20, 2023

+1 on this question!

@lucacasonato With some guidance, I could invest some time to update it from time to time.

@o-az
Copy link

o-az commented May 3, 2023

If anyone is open to collaborating, I'm considering forking this repo as it seems to be unmaintained.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants