4 ms·
I would definitely recommend puppeteer if you can, it's maintained by the Chrome team and always does things the "approved way". The only reason we did playwrig
by nikisweeting 1y ago
I would definitely recommend puppeteer if you can, it's maintained by the Chrome team and always does things the "approved way". The only reason we did playwright is because we're a python library and pyppeteer was abandoned.
- cebert 1y agoMost of the Puppeteer team left and joined Playwright under Microsoft.
- nikisweeting 1y agoWhile that is the origin story of Playwright in 2020, that's no longer really true. Puppeteer is alive and well and arguably moving faster than Playwright these days because it's updated in lockstep with https://github.com/ChromeDevTools/devtools-frontend https://github.com/ChromeDevTools/devtools-frontend
- tbrockman 1y agoAlso recently found it unnecessarily difficult to do profiling of page workers using Playwright's CDPSession wrapper (and they don't seem to have any plans to improve it: https://github.com/microsoft/playwright/issues/22992#issuecomment-1548112434 https://github.com/microsoft/playwright/issues/22992#issueco...), whereas it was pretty painless in Puppeteer. So, definitely more useful if you care about more than just your main thread.