3 ms·
We experimented moving to Playwright but Playwright doesn't handle long-running browser sessions well, as the devs have (maybe rightly) prioritized its use for
by tw4l 3y ago
We experimented moving to Playwright but Playwright doesn't handle long-running browser sessions well, as the devs have (maybe rightly) prioritized its use for testing over archival use cases and want you to spin up a browser each time. For archival purposes, that doesn't work as well because we're not able to save the browser profile to retain cookies such as login credentials, so we've moved back to using Puppeteer for now.
- niam 3y agoAnswered my next question before I even asked it. As a next-next question: May I ask what y'all experienced with long-running browser sessions? Or what in particular led you to believe it was unfit for this purpose?
- ikreymer 3y agoMemory usage increases for long-running session, see this issue for more details: https://github.com/microsoft/playwright/issues/6319 https://github.com/microsoft/playwright/issues/6319
- andrewmackrodt 3y agoYou can use launchPersistentContext and define a custom user directory to maintain profile state: https://playwright.dev/docs/api/class-browsertype#browser-type-launch-persistent-context https://playwright.dev/docs/api/class-browsertype#browser-ty...