Matchu ea8791c69d Create a new browser for each assetImage request ... 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"! 😅		2021-09-02 19:25:48 -07:00
..
allWakaValues.js	Trickier disabling honeycomb instrumentation	2021-08-08 00:23:57 -07:00
assetImage.js	Create a new browser for each assetImage request	2021-09-02 19:25:48 -07:00
graphql.js	Trickier disabling honeycomb instrumentation	2021-08-08 00:23:57 -07:00
outfitImage.js	Trickier disabling honeycomb instrumentation	2021-08-08 00:23:57 -07:00
outfitPageSSR.js	Trickier disabling honeycomb instrumentation	2021-08-08 00:23:57 -07:00
sendFeedback.js	Trickier disabling honeycomb instrumentation	2021-08-08 00:23:57 -07:00
uploadLayerImage.js	Trickier disabling honeycomb instrumentation	2021-08-08 00:23:57 -07:00
validPetPoses.js	Trickier disabling honeycomb instrumentation	2021-08-08 00:23:57 -07:00