Matchu
ea8791c69d
Well, holding onto the browser instance seems to be a source of bugs (my previous fix didn't seem to fix it), and I'm not _sure_ what the perf characteristics are, so let's just try a fresh instance each time!
I don't actually know what a browser "instance" in Playwright really is, I'm not sure it even necessarily creates a new process, I just don't know
and I saw some Vercel example code take this approach, which is definitely simpler, and I guess must not be _overtly_ bad perf if it's idiomatic?
So, like, ok, cool, let's see if this stops 500ing us with "Browser closed"! 😅
|
||
---|---|---|
.. | ||
allWakaValues.js | ||
assetImage.js | ||
graphql.js | ||
outfitImage.js | ||
outfitPageSSR.js | ||
sendFeedback.js | ||
uploadLayerImage.js | ||
validPetPoses.js |